$ECHO variations (was: FYI: IRIX 6.5 and exporting symbols.)

2005-03-24 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Thu, Mar 24, 2005 at 09:15:35AM CET: > Well, this is kind of Libtool-specific, as we use one of > echo > print -r > printf %s\n > $CONFIG_SHELL $0 --fallback-echo > > for $ECHO, and the third one at least does the wrong thing with more > than one argument, and th

Re: FYI: IRIX 6.5 and exporting symbols.

2005-03-24 Thread Ralf Wildenhues
Hi Noah, Peter, others, * Noah Misch wrote on Thu, Mar 24, 2005 at 04:04:51AM CET: > On Sun, Mar 20, 2005 at 08:18:48AM +0100, Ralf Wildenhues wrote: > > > Ralf Wildenhues wrote: > > > > This is not ok: $ECHO may only take one argument, so you must > > What systems have that problem? What do th

Re: FYI: IRIX 6.5 and exporting symbols.

2005-03-23 Thread Noah Misch
Hi Ralf, On Sun, Mar 20, 2005 at 08:18:48AM +0100, Ralf Wildenhues wrote: > > Ralf Wildenhues wrote: > > > This is not ok: $ECHO may only take one argument, so you must What systems have that problem? What do they do with the latter arguments? > > > double-quote. Furthermore, the argument may

Re: FYI: IRIX 6.5 and exporting symbols.

2005-03-19 Thread Ralf Wildenhues
Hi Peter, * Peter Ekberg wrote on Thu, Mar 17, 2005 at 04:27:28PM CET: > Ralf Wildenhues wrote: > > > This is not ok: $ECHO may only take one argument, so you must > > double-quote. Furthermore, the argument may not start with a hyphen > > in general, for it might be misinterpreted as option to

RE: FYI: IRIX 6.5 and exporting symbols.

2005-03-17 Thread Peter Ekberg
Ralf Wildenhues wrote: > No, wait. *snip* > This is not ok: $ECHO may only take one argument, so you must > double-quote. Furthermore, the argument may not start with a hyphen > in general, for it might be misinterpreted as option to the $ECHO > command. The solution is to use the slower > $E

Re: FYI: IRIX 6.5 and exporting symbols.

2005-03-17 Thread Ralf Wildenhues
No, wait. * Ralf Wildenhues wrote on Thu, Mar 17, 2005 at 01:21:57PM CET: > * Peter Ekberg wrote on Thu, Mar 17, 2005 at 12:45:18PM CET: > > > > > > 2005-03-10 Peter Ekberg > > > > > > * m4/libtool.m4 (_LT_LINKER_SHLIBS): Test if it is > > > possible to use the -exports_file linker option

FYI: IRIX 6.5 and exporting symbols.

2005-03-17 Thread Ralf Wildenhues
Hi Peter, * Peter Ekberg wrote on Thu, Mar 17, 2005 at 12:45:18PM CET: > I wrote: > > > > 2005-03-10 Peter Ekberg > > > > * m4/libtool.m4 (_LT_LINKER_SHLIBS): Test if it is > > possible to use the -exports_file linker option on > > irix with gcc, as the gcc specs file may include

RE: IRIX 6.5 and exporting symbols.

2005-03-17 Thread Peter Ekberg
I wrote: > Here's a new patch that tries to link a DSO and explicitly > exporting its sole function. The patch uses -exported_symbol > for the test instead of -exports_file, but that is equivalent. > > > 2005-03-10 Peter Ekberg > > * m4/libtool.m4 (_LT_LINKER_SHLIBS): Test if it is >

RE: IRIX 6.5 and exporting symbols.

2005-03-10 Thread Peter Ekberg
Albert Chin wrote: > On Wed, Mar 09, 2005 at 02:51:31PM +0100, Ralf Wildenhues wrote: >> * Peter Ekberg wrote on Wed, Mar 09, 2005 at 02:11:40PM CET: >>> This makes it work for me, the namespace is sadly polluted, >>> but there is nothing we can do about that, short of hacking >>> the gcc specs fil

RE: IRIX 6.5 and exporting symbols.

2005-03-10 Thread Peter Ekberg
Ralf Wildenhues wrote: > Michael -- this might be of interest for you. Quoting > generously since > the ML archives don't provide me with a link yet. > *snip* > Preprocess a file with __GNUC__ (and __GNUC_MINOR__ if necessary). > Maybe we can abandon that idea in favor of just running the linker

Re: IRIX 6.5 and exporting symbols.

2005-03-09 Thread Albert Chin
On Wed, Mar 09, 2005 at 02:51:31PM +0100, Ralf Wildenhues wrote: > * Peter Ekberg wrote on Wed, Mar 09, 2005 at 02:11:40PM CET: > > This makes it work for me, the namespace is sadly polluted, > > but there is nothing we can do about that, short of hacking > > the gcc specs file or wait for gcc 3.5/

Re: IRIX 6.5 and exporting symbols.

2005-03-09 Thread Ralf Wildenhues
Michael -- this might be of interest for you. Quoting generously since the ML archives don't provide me with a link yet. * Peter Ekberg wrote on Wed, Mar 09, 2005 at 03:14:46PM CET: > Ralf Wildenhues wrote: > > * Peter Ekberg wrote on Wed, Mar 09, 2005 at 02:11:40PM CET: > >> On 2005-01-13, I wro

RE: IRIX 6.5 and exporting symbols.

2005-03-09 Thread Peter Ekberg
Ralf Wildenhues wrote: > Hi Peter, > > * Peter Ekberg wrote on Wed, Mar 09, 2005 at 02:11:40PM CET: >> On 2005-01-13, I wrote: >>> >>> gcc -v -shared .libs/cleanup.o .libs/cleanup_stubs.o .libs/cpuid.o >>> .libs/conf.o .libs/debug.o .libs/dl.o .libs/init.o .libs/misc.o >>> .libs/parse.o .libs/str

Re: IRIX 6.5 and exporting symbols.

2005-03-09 Thread Ralf Wildenhues
Hi Peter, * Peter Ekberg wrote on Wed, Mar 09, 2005 at 02:11:40PM CET: > On 2005-01-13, I wrote: > > > > gcc -v -shared .libs/cleanup.o .libs/cleanup_stubs.o .libs/cpuid.o > > .libs/conf.o .libs/debug.o .libs/dl.o .libs/init.o .libs/misc.o > > .libs/parse.o .libs/string.o .libs/time.o .libs/task.

RE: IRIX 6.5 and exporting symbols.

2005-03-09 Thread Peter Ekberg
On 2005-01-13, I wrote: > Albert Chin wrote: >> Please rerun with -v so we see who gcc is calling. > > gcc -v -shared .libs/cleanup.o .libs/cleanup_stubs.o .libs/cpuid.o > .libs/conf.o .libs/debug.o .libs/dl.o .libs/init.o .libs/misc.o > .libs/parse.o .libs/string.o .libs/time.o .libs/task.o .libs