Re: CC can be a program name *with arguments*

2005-03-03 Thread Bob Friesenhahn
On Thu, 3 Mar 2005, Alexandre Oliva wrote: On Mar 3, 2005, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: In making this decision, we must consider what existing Automake does. If it searches for installed libtool by looking for a 'libtool' program in the path, then there will be problems. Automake us

Re: CC can be a program name *with arguments*

2005-03-03 Thread Alexandre Oliva
On Mar 3, 2005, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: > In making this decision, we must consider what existing Automake > does. If it searches for installed libtool by looking for a 'libtool' > program in the path, then there will be problems. Automake uses libtool the way it was designed

◇◆夜の情報募集◇◆

2005-03-03 Thread [EMAIL PROTECTED]
$B!!!z(B.$B!'!&(B*.$B!&!%(B:$B!y(B.$B!'!&(B*.$B!&!%(B:$B!z(B.$B!'!&(B*.$B!&!%(B:$B!y(B.$B!'!&(B*.$B!&!%(B:$B!z(B.$B!'!&(B*.$B!&!%!y(B.$B!'!&(B $B(B $B!D!E!&(B $B(6(6!!Lk$N>pJsJg=8$N3'MM$X(6(6!&!E!D(B $B!!":";":";":!!"!!~:#G/

Re: CC can be a program name *with arguments*

2005-03-03 Thread Albert Chin
On Thu, Mar 03, 2005 at 01:49:20AM -0500, Charles Wilson wrote: > I have a few concerns about removing this functionality: namely, I > maintain a bunch of cygwin packages, and some of those use libtool but > not automake (nor, in one case, autoconf). Namely, libjpeg(*) and > ncurses; I'm sure t

Re: FYI: be careful to follow links during libltdl install [libtool--release--2.0--patch-51]

2005-03-03 Thread Bob Friesenhahn
On Wed, 2 Mar 2005, Noah Misch wrote: On the other hand, the extraction invocation probably does need `o' to make Unix tar reset file ownership (e.g., when an unprivileged user builds libtool and then installs it as root). On my Gentoo Linux box (which uses GNU tar 1.14, released in 2004) the tra

Re: CC can be a program name *with arguments*

2005-03-03 Thread Bob Friesenhahn
On Thu, 3 Mar 2005, Gary V. Vaughan wrote: Very well, then let's put it to the vote! I never use the installed libtool myself, and can't think of a compelling reason to keep it around that outweighs the misunderstandings that it causes. But, on the other hand I'm not sure I want to rock the boat

Re: FYI: be careful to follow links during libltdl install [libtool--release--2.0--patch-51]

2005-03-03 Thread Gary V. Vaughan
Hi Noah! Noah Misch wrote: > On Wed, Mar 02, 2005 at 10:34:19AM +, Gary V. Vaughan wrote: > >> ## with libtoolize, we have to preserve their timestamps carefully: >> install-data-local: >> $(mkinstalldirs) $(DESTDIR)$(ltdldatadir) >> - ( cd $(srcdir) && $(AMTAR) cf - $(ltdldatafil

Re: CC can be a program name *with arguments*

2005-03-03 Thread Gary V. Vaughan
Hi Chuck, Charles Wilson wrote: > Gary V. Vaughan wrote: > >> +0.5 to remove installed libtool script in HEAD >> -0.5 for branch-2-0 >> -1 for branch-1-5 > > > -1 HEAD > -1 branch-2-0 > -1 branch-1-5 > > I have a few concerns about removing this functionality: namely, I > maintain a bunch of

Re: CC can be a program name *with arguments*

2005-03-03 Thread Gary V. Vaughan
Salut Alexandre! Alexandre Duret-Lutz wrote: > On Thu, Mar 03, 2005 at 12:52:14AM +, Gary V. Vaughan wrote: > >>I never use the installed libtool myself, and can't think of a >>compelling reason to keep it around that outweighs the >>misunderstandings that it causes. > > > Is `libtool --mod

Re: CC can be a program name *with arguments*

2005-03-03 Thread Alexandre Duret-Lutz
On Thu, Mar 03, 2005 at 12:52:14AM +, Gary V. Vaughan wrote: > > I never use the installed libtool myself, and can't think of a > compelling reason to keep it around that outweighs the > misunderstandings that it causes. Is `libtool --mode=execute gdb ...' subject to the errors you are discuss