Choose destination directory at installation
Sauterel Fabrice
--===============1953672124==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C6F35A.C995A224"
This is a multi-part message in MIME format.
------_=_NextPart_001_01C6F35A.C995A224
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Hi,
I would like to choose the directory where to install the snmpd agent
during the installation (i.e. make install) and not at configuration
time (i.e. ./configure).=20
Is it possible to do that??? How?=20
Actually I would like to be able to package my agent and to be able to
install it wherever I want.=20
Thanks in advance - Fabrice
------_=_NextPart_001_01C6F35A.C995A224
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.28">
<TITLE>Choose destination directory at installation</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=3D2 FACE=3D"Arial">Hi,</FONT>
</P>
<P><SPAN LANG=3D"fr-ch"><FONT SIZE=3D2 FACE=3D"Arial">I would like to =
choose the directory where to install the snmpd agent during the =
installation (i.e. make install) and not at configuration time (i.e. =
./configure). </FONT></SPAN></P>
<P><SPAN LANG=3D"fr-ch"><FONT SIZE=3D2 FACE=3D"Arial">Is it possible to =
do that??? How? </FONT></SPAN>
<BR><SPAN LANG=3D"fr-ch"><FONT SIZE=3D2 FACE=3D"Arial">Actually I would =
like to be able to package my agent and to be able to install it =
wherever I want. </FONT></SPAN>
<BR><SPAN LANG=3D"fr-ch"><FONT SIZE=3D2 FACE=3D"Arial">Thanks in advance =
- Fabrice</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C6F35A.C995A224--
--===============1953672124==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--===============1953672124==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Net-snmp-users mailing list
Net-snm...@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
--===============1953672124==--
Dave Shield
> I would like to choose the directory where to install the snmpd agent during
> the installation (i.e. make install) and not at configuration time (i.e.
> ./configure).
Try
make install DESTDIR=/some/where/else
Dave
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Sauterel Fabrice
./configure script, then typing "make install DESTDIR=/some/where/else"
will install the agent in /some/where/else/myPrefix
If I do not specify any prefix, then typing "make install
DESTDIR=/some/where/else" will install it in /some/where/else/usr/local
I would like my root to be /some/where/else
And then:
/some/where/else/bin
/some/where/else/include
/some/where/else/sbin
etc...
Thomas Anders
> The problem remains... If I specify a "--prefix=myPrefix" for the
> ./configure script, then typing "make install DESTDIR=/some/where/else"
> will install the agent in /some/where/else/myPrefix
>
> If I do not specify any prefix, then typing "make install
> DESTDIR=/some/where/else" will install it in /some/where/else/usr/local
>
> I would like my root to be /some/where/else
> And then:
> /some/where/else/bin
> /some/where/else/include
> /some/where/else/sbin
> etc...
Then you need to configure --prefix=/some/where/else. These paths get hard-coded
into the toolkit, so you cannot change them (permanently) at install time.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
Sauterel Fabrice
Is it also "hard-coded" in binaries and libraries??? Or just in
"readable" text files in case I could write a script to identify and
replace it.
Does it mean that everytime we want to change to install directory, we
have again to "configure, make and make install"???
>Then you need to configure --prefix=/some/where/else. These paths get
hard-coded into the toolkit, so you cannot
>changethem(permanently) at install time.
-------------------------------------------------------------------------
holger...@bt.com
> Sauterel Fabrice wrote:
> > The problem remains... If I specify a "--prefix=myPrefix" for the
> > ./configure script, then typing "make install
> > DESTDIR=/some/where/else" will install the agent in
> > /some/where/else/myPrefix
> >
> > If I do not specify any prefix, then typing "make install
> > DESTDIR=/some/where/else" will install it in
> > /some/where/else/usr/local
> >
> > I would like my root to be /some/where/else
> > And then:
> > /some/where/else/bin
> > /some/where/else/include
> > /some/where/else/sbin
> > etc...
>
>
>
Accoding to ./configure --help you can use the following options:
Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--datadir=DIR read-only architecture-independent data
[PREFIX/share]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data
[PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--infodir=DIR info documentation [PREFIX/info]
--mandir=DIR man documentation [PREFIX/man]
I have never actually used any of those though.
Regards,
Holger
Frank, Jason
I do this all of the time to handle package building on Solaris.
Basically, you install into a temporary directory and create your
package off of that. Here's what I use:
make install prefix=${TMP}/${prefix} exec_prefix=${TMP}${prefix}
In my case, the value of $prefix is the same prefix that was passed into
configure. So, your question about changing paths doesn't really apply
to my situation.
But I can't think of any paths that get hardcoded in the programs
anywhere. Net-SNMP doesn't use a .pc file, and I'm not sure what else
there might be that would need to be fixed. You'll have to set your
LD_LIBRARY_PATH, PATH, and MANPATH appropriately if you chose some
whacky install dir, but that's whether it's done at configure or install
time.
Jason
-----Original Message-----
From: net-snmp-us...@lists.sourceforge.net
[mailto:net-snmp-us...@lists.sourceforge.net] On Behalf Of
Sauterel Fabrice
Sent: Thursday, October 19, 2006 8:23 AM
To: net-snm...@lists.sourceforge.net
Subject: RE: Choose destination directory at installation
Thanks for the answer Dave and Thomas!
Is it also "hard-coded" in binaries and libraries??? Or just in
"readable" text files in case I could write a script to identify and
replace it.
Does it mean that everytime we want to change to install directory, we
have again to "configure, make and make install"???
>Then you need to configure --prefix=/some/where/else. These paths get
hard-coded into the toolkit, so you cannot
>changethem(permanently) at install time.
------------------------------------------------------------------------
-
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-users mailing list
Net-snm...@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
<font size="1" face="arial">This message (including any attachments) may contain confidential or otherwise privileged information and is intended only for the individual(s) to which it is addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message or that arise as a result of e-mail transmission. If verification is required please request a hard-copy version from the sender.
SOURCECORP, Incorporated
www.srcp.com
</font>
Sauterel Fabrice
before make install.
I am trying to find a way to change the directory tree after compilation
(that is also after configure) so as to be able to create independent
package.
Regards,
Fabrice
>Accoding to ./configure --help you can use the following options:
>Fine tuning of the installation directories:
> --bindir=DIR user executables [EPREFIX/bin]
> --sbindir=DIR system admin executables [EPREFIX/sbin]
> --libexecdir=DIR program executables [EPREFIX/libexec]
> --datadir=DIR read-only architecture-independent data
>[PREFIX/share]
> --sysconfdir=DIR read-only single-machine data [PREFIX/etc]
> --sharedstatedir=DIR modifiable architecture-independent data
>[PREFIX/com]
> --localstatedir=DIR modifiable single-machine data [PREFIX/var]
> --libdir=DIR object code libraries [EPREFIX/lib]
> --includedir=DIR C header files [PREFIX/include]
> --oldincludedir=DIR C header files for non-gcc [/usr/include]
> --infodir=DIR info documentation [PREFIX/info]
> --mandir=DIR man documentation [PREFIX/man]
>
>I have never actually used any of those though.
>
>Regards,
>
>Holger
-------------------------------------------------------------------------
Sauterel Fabrice
Then make
And then make install prefix=/tmp/some/where/else
exec-prefix=/tmp/some/where/else (that is different from 'configure')
Then the directories 'include', 'share' etc.. are indeed moved to
/tmp/some/where/else BUT 'bin', 'sbin' and 'lib' are still built under
/here/. It seem that the directive exec-prefix does not work with "make
install"
FYI: I am running net-snmp-5.2.3 under IBM AIX-5.3
Regards - Fabrice
>I do this all of the time to handle package building on Solaris.
>Basically, you install into a temporary directory and create your
package off of that. Here's what I use:
>
>make install prefix=${TMP}/${prefix} exec_prefix=${TMP}${prefix}
>
>In my case, the value of $prefix is the same prefix that was passed
into configure. So, your question about changing paths doesn't >really
apply to my situation.
>
>But I can't think of any paths that get hardcoded in the programs
anywhere. Net-SNMP doesn't use a .pc file, and I'm not sure what
>else there might be that would need to be fixed. You'll have to set
your LD_LIBRARY_PATH, PATH, and MANPATH appropriately if you
>chose some whacky install dir, but that's whether it's done at
configure or install time.
>
>Jason
-------------------------------------------------------------------------
Sauterel Fabrice
Sorry for my misunderstanding...
I typed "make install prefix=/myDir/ exec-prefix=/myDir/ " instead of
exec_prefix=/myDir/ (underscore!!!!!) then it is working well. That is,
everything is installed in /myDir/
But then if I look, e.g., in the following file /myDir/lib/libnetsnmp.la
it still contains this
....
# Directory that this library needs to be installed in:
libdir=/the_prefix_I_gave_to_the_configure_script/
It also seems that sbin/snmpd still depends on the prefix I gave to the
configure script.
Any ideas?
Dave Shield
> exec_prefix=/myDir/ (underscore!!!!!) then it is working well. That is,
> everything is installed in /myDir/
> But then if I look, e.g., in the following file /myDir/lib/libnetsnmp.la
> it still contains this
> ....
> # Directory that this library needs to be installed in:
> libdir=/the_prefix_I_gave_to_the_configure_script/
> It also seems that sbin/snmpd still depends on the prefix I gave to the
> configure script.
That is correct.
The purpose of "prefix" and "exec_prefix" is to help with building packages,
where there may already be another installed version of the software on the same
system (which should not interfere with the version being packaged, or
vice versa).
These are purely temporary during the packaging process, and should be
invisible once the resulting package has been installed on the destination
system(s).
The final location of the software should match what was specified to configure.
It *might* be possible to install some things elsewhere (especially if binaries
are linked statically), but I can't help feeling that you're trying to
stretch the
installation process beyond what is reasonable.
Dave