>> -----Original Message-----
>> From: James Pratt [mailto:jpr...@norwich.edu]
>> Sent: Monday, July 27, 2009 10:41 PM
>> To: Matthew Tice; nagios-users@lists.sourceforge.net
>> Subject: Re: [Nagios-users] Static linked libraries
>>
>>
>>
>> >> -----Original Message-----
>> >> From: Matthew Tice [mailto:mjt...@gmail.com]
>> >> Sent: Monday, July 27, 2009 10:29 PM
>> >> To: nagios-users@lists.sourceforge.net
>> >> Subject: [Nagios-users] Static linked libraries
>> >>
>> >> Hello, I'd like to compile Nagios and the Nagios plugins with
static
>> linked libraries. Is
>> >> this possible? I couldn't find any documentation regarding it and
my
>> understanding
>> >> of gcc is shoddy at best. If it is possible then a few examples
>> would be appreciated.
>> >>
>> >> Thanks,
>> >> Matt
>>
>> Sure, try:
>>
>> ./configure --disable-shared --whatever-here-etc
>>
>> Cheers,
>> Jamie
Ok, sorry, but before I send anyone who is admitting "shoddy" knowledge
of GCC down this road, just be aware of (among other things):
* Because linked external programs are built into the executable
files, these files become larger.
* You cannot change the behavior of executable files without
relinking them.
* External called programs cannot be shared. Therefore, if more than
one calling program needs to access the called programs, duplicate
copies of the called programs must be loaded in memory.
Ps - run "./configure --help" to see all of the available nagios-plugin
compile options...
Cheers,, x2
Jamie
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
