Larry Rosenman writes: > YUP, it's LD_LIBRARY_PATH. That's odd. On my system (and on all others that I've heard of that have it) this only affects the runtime linker, not the "ld" linker. > We need to make sure that the BUILD Unsets it... Are you sure that this can't lead to failures if a program run during the build requires this to be set. (Something like tclsh comes to mind.) Seems like something you ought to do manually. -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
- Re: [HACKERS] more multibyte/After TGL... Larry Rosenman
- Re: [HACKERS] more multibyte/After TGL... Tatsuo Ishii
- Re: [HACKERS] more multibyte/After TGL... Larry Rosenman
- Re: [HACKERS] more multibyte/After TGL... Larry Rosenman
- Re: [HACKERS] more multibyte/After TGL... Tom Lane
- Re: [HACKERS] more multibyte/After TGL... Larry Rosenman
- Re: [HACKERS] more multibyte/After TGL... Tom Lane
- Re: [HACKERS] more multibyte/After TGL... Larry Rosenman
- Re: [HACKERS] more multibyte/After TGL... Larry Rosenman
- Re: [HACKERS] more multibyte/After TGL... Larry Rosenman
- Re: [HACKERS] more multibyte/After TGL... Peter Eisentraut
- Re: [HACKERS] more multibyte/After TGL... Larry Rosenman
- Re: [HACKERS] more multibyte/After TGL... Peter Eisentraut
- Re: [HACKERS] more multibyte/After TGL... Larry Rosenman