Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*building\s+2\.4\.4p1\s+under\s+Solaris\s+9\s+with\s+native\-built\s+gcc\-3\.3\s+$fwd$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*building\s+2\.4\.4p1\s+under\s+Solaris\s+9\s+with\s+native\-built\s+gcc\-3\.3\s+$fwd$\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: building 2.4.4p1 under Solaris 9 with native-built gcc-3.3 (fwd) (score: 1): Author: Craig Dewick <cdewick AT lios.apana.org DOT au>; Date: Thu, 31 Jul 2003 07:45:54 +1000 (EST); Further to this issue, I have now tried, for the sake of experimentation (after a few people have contacted me privately suggesting it), setting LD_LIBRARY_PATH. I set it just to have /usr/local/lib; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2003-07/msg00726.html (11,952 bytes)
2. Re: building 2.4.4p1 under Solaris 9 with native-built gcc-3.3 (fwd) (score: 1): Author: Ean Kingston <ean AT hedron DOT org>; Date: 30 Jul 2003 22:10:08 -0400; As I understand things. The LD_LIBRARY_PATH variable is used at run time as an additional search path for loadable modules (.so files). If you have it set while compiling, it will search that path fo; /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2003-07/msg00729.html (11,541 bytes)

Current List: 1 - 2
Page: [1]