Re: [shell functions, was RE: solving of name conflicts in included.a]

2002-11-14 Thread Bruce Korb
Akim Demaille wrote: > I don't agree. Autoconf does not use shell functions, it just says it > will some day. If you want to use shell functions, don't do it > pretending Autoconf did first :) > > Also, Autoconf will try to find a shell that supports functions. Someone made the assertion that t

Re: tabularized libtool

2002-11-14 Thread Bruce Korb
Tom Lord wrote: > Finally, I still wish that a side-effect of the libtool effort was a > document/database that explained clearly and concisely how to deal > with shared libraries in various environments. As it stands, that > information is weaved into convoluted code and the situation is > glos

Re: getting a locally built library

2002-11-14 Thread David Bacher
On Thursday, November 14, 2002, at 11:36 AM, Bruce Korb wrote: You're specifically adding -L/sw/lib. Don't. It will get added by the configure script in the right place automatically, as long as /sw/bin/guile-config and xml2-config are properly found with the PATH variable. Gotcha. Removing

Re: getting a locally built library

2002-11-14 Thread David Bacher
On Thursday, November 14, 2002, at 08:39 AM, Alexandre Duret-Lutz wrote: David, could you explain where `-L../autoopts/.libs -lopts' comes from? Sure. Here are my original libtool link and compiler link commands: /bin/sh ../libtool --mode=link gcc -g -O2 -L/sw/lib -o autogen autogen-opts.o

Re: ltconfig generation change for SCO builds

2002-11-14 Thread Bob Friesenhahn
The next release of libtool does not use 'ltconfig'. You might want to check libtool out of CVS and see what changes need to be made (if any). Bob On Thu, 14 Nov 2002, Jonathan Schilling wrote: > To the libtool maintainers, > > A change needs to be made to the generation of ltconfig in order fo

Re: [shell functions, was RE: solving of name conflicts in included.a]

2002-11-14 Thread Charles Wilson
[EMAIL PROTECTED] wrote: Let them install BASH and get out of our way. Both of them. Bash uses configure. And so does ash :-( which was my first thought for working around this problem. On the other hand, is it so terrible to ask that those who wish to continue using systems with 20-ye

Re: [shell functions, was RE: solving of name conflicts in included.a]

2002-11-14 Thread Tom Lord
> Let them install BASH and get out of our way. As someone else pointed out, bash uses autoconf. Also, while its good to talk about bringing up GNU environments on top of proprietary ones, the long term view is to also think about bringing them up on raw iron. So, pick a small set of pr

ltconfig generation change for SCO builds

2002-11-14 Thread Jonathan Schilling
To the libtool maintainers, A change needs to be made to the generation of ltconfig in order for it to build correctly on SCO OpenServer when using the SCO UDK development kit (which is a different [more advanced] development kit than the "regular" one that comes with OpenServer). The change

Re: [shell functions, was RE: solving of name conflicts in included.a]

2002-11-14 Thread Akim Demaille
> "Robert" == Robert Boehne <[EMAIL PROTECTED]> writes: Robert> All, Hey, that's a relief, now we don't have to deal with this Robert> issue anymore. I would be in favor of a) leaving the shell Robert> functions in place, and b) making use of them more. I don't agree. Autoconf does not use

Re: getting a locally built library

2002-11-14 Thread Bruce Korb
Alexandre Duret-Lutz wrote: > >> /bin/sh ../libtool --mode=link gcc -g -O2 -L/sw/lib -o autogen \ > >> -export-dynamic -lguile *.o -L/sw/lib -lguile -lm \ > >> -L../autoopts/.libs -lopts -ldl > >> ld: Undefined symbols: > >> _aopts_alloc > >> _aopts_realloc > >> _aopts_strdup > >> make[1

Autoconf 2.55 is released!

2002-11-14 Thread Akim Demaille
The Autoconf team -- Akim, Alexandre, Jim, Paul, and Tom -- is happy to annonce the birth of Autoconf 2.55. Download, compile, install, torture, and enjoy! - Why should I upgrade from 2.54? A few bug fixes, improved portability, no known incompatibility with 2.54 and 2.55, forthcoming Gettex

Re: getting a locally built library

2002-11-14 Thread Alexandre Duret-Lutz
>>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes: Bruce> Alexandre Duret-Lutz wrote: >> >> /bin/sh ../libtool --mode=link gcc -g -O2 -L/sw/lib -o autogen \ >> >> -export-dynamic -lguile *.o -L/sw/lib -lguile -lm \ >> >> -L../autoopts/.libs -lopts -ldl >> >> ld: Undefined symbols: >> >

Re: getting a locally built library

2002-11-14 Thread Bruce Korb
David Bacher wrote: There's the problem: > Configure parameters: > CPPFLAGS=-I/sw/include > LDFLAGS=-L/sw/lib > --prefix=/sw > --enable-snprintfv-install > --mandir=/sw/share/man > --infodir=/sw/share/info You're specifically adding -L/sw/lib. Don't. It will get added by the configure script in

Re: [shell functions, was RE: solving of name conflicts in included.a]

2002-11-14 Thread akim
On Thu, Nov 14, 2002 at 07:53:42AM -0800, Bruce Korb wrote: > Akim Demaille wrote: > > I don't agree. Autoconf does not use shell functions, it just says it > > will some day. If you want to use shell functions, don't do it > > pretending Autoconf did first :) > > > > Also, Autoconf will try to

Re: getting a locally built library

2002-11-14 Thread Alexandre Duret-Lutz
>>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes: Bruce> David Bacher wrote: [...] >> /bin/sh ../libtool --mode=link gcc -g -O2 -L/sw/lib -o autogen \ >> -export-dynamic -lguile *.o -L/sw/lib -lguile -lm \ >> -L../autoopts/.libs -lopts -ldl >> ld: Undefined symbols: >> _aopts_alloc

Re: [shell functions, was RE: solving of name conflicts in included.a]

2002-11-14 Thread Bruce Korb
[EMAIL PROTECTED] wrote: > Bash uses configure. Bootstrap-Bash could use a frozen version of configure. There certainly won't be any additions to the list of systems with 15+ year old shells, so a bootstrap-bash for hobbyists should work just fine. __