Fw: ROSINHA AUSENTE

Gente...assim já é demais...   Fábio   - Original Message - From: Ricardo Silva  To: Fábio Schult Sent: Monday, February 21, 2005 10:34 PM Subject: ROSINHA AUSENTE O ESTADO DO RIO ESTÁ SEM GOVERNANTE! Há mais de 2 meses a Governadora Rosinha, não trabalha mais com

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

On Tue, 1 Mar 2005, Ralf Wildenhues wrote: Sure. But we are talking about m4/libtool.m4, right? This happens at configure time. I want, in a libtoolized project, ../configure CC='pgcc-78.9 -foo-option' to succeed in choosing Portland compiler options. No multiple compilers involved here. Libtool

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

On Tue, 1 Mar 2005, Gary V. Vaughan wrote: You guys ever encountered a system with compilers named gcc-3.4.1 gcc-3.4.2 icc-8.1 ... Yep, but you would need to build a different libtool for each compiler. Relying on the compiler checks performed on one working for another is likely to cause t

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

Hallo Ralf! Ralf Wildenhues wrote: >>>You guys ever encountered a system with compilers named >>> gcc-3.4.1 >>> gcc-3.4.2 >>> icc-8.1 >>> ... >> >>Yep, but you would need to build a different libtool for each compiler. >>Relying on the compiler checks performed on one working for another is >>

Re: 115-gary-libtoolize-copy-fix.patch

Hi Gary, * Gary V. Vaughan wrote on Tue, Mar 01, 2005 at 02:06:33PM CET: > Ralf Wildenhues wrote: > > > * Gary V. Vaughan wrote on Tue, Feb 22, 2005 at 02:19:39PM CET: > > | +elif { ( cd "$my_srcdir" && $TAR cf - "$my_file" > /dev/null 2>&1; ) > > \ > > | +| ( cd "$my_destdir" && "$T

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

Hi Gary, * Gary V. Vaughan wrote on Tue, Mar 01, 2005 at 02:04:51PM CET: > > Welcome back :-) Thanks! (freezing) > > * Gary V. Vaughan wrote on Fri, Feb 25, 2005 at 01:21:14PM CET: > >>Bob Friesenhahn wrote: > >> > >>My thoughts exactly. cc_basename is only ever used in case statements, > >>s

Re: 115-gary-libtoolize-copy-fix.patch

Ralf Wildenhues wrote: > Hi Gary, Hallo! > * Gary V. Vaughan wrote on Tue, Feb 22, 2005 at 02:19:39PM CET: > | +elif { ( cd "$my_srcdir" && $TAR cf - "$my_file" > /dev/null 2>&1; ) \ > | +| ( cd "$my_destdir" && "$TAR" xf - > /dev/null 2>&1; ) } ; then > > Just don't ever let anyone

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

Ralf Wildenhues wrote: > Hi guys, Hallo Ralf! Welcome back :-) > * Gary V. Vaughan wrote on Fri, Feb 25, 2005 at 01:21:14PM CET: > >>Bob Friesenhahn wrote: >> >>>On Thu, 24 Feb 2005, Peter O'Gorman wrote: >>> >>> Okay to apply to branch-1-5 and then forward port? >>> >>>Doesn't it make most

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

Hi guys, * Gary V. Vaughan wrote on Fri, Feb 25, 2005 at 01:21:14PM CET: > Bob Friesenhahn wrote: > > On Thu, 24 Feb 2005, Peter O'Gorman wrote: > > > >> Okay to apply to branch-1-5 and then forward port? > > > > Doesn't it make most sense to fix cc_basename so that it doesn't include > > any tr

Re: 115-gary-libtoolize-copy-fix.patch

Hi Gary, (working on mail backlog..) * Gary V. Vaughan wrote on Tue, Feb 22, 2005 at 02:19:39PM CET: | | # func_copy_cb filename srcdir destdir | -# A wrapper for func_copy that accepts arguments in the order | -# used by func_copy_all_files callbacks. | +# If option `--copy' was specified, or s