Re: Patch for Portland compiler support

* Jeff Squyres wrote on Wed, Nov 17, 2004 at 06:30:27PM CET: > Actually, before I attempt the LT 2.x patch, how does this look for the > 1.5 patch? I checked pgcc, pgCC, pgf77, and pgf90, both in the 1.5 > test suite (I assuming that configuring LT with CC=pgcc [etc.] and then > "make check" is

■噂の特だね！！ただだよ！ドットコム■創刊号

$B(.!z!y(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,!z!y(/(B (B [EMAIL PROTECTED]@[EMAIL PROTECTED](B2004.11$BH/9T!d(B $B(1!z!y(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,!z!y(0(B (B $B!y(B1,351,792$BItH/9T!y(B (B $B!!!

Using libtool 2.0 in autoconf tests

Hi, I have send this question to the list about a month ago, but unfortunately, there hasn't been an answer yet, and the release of libtool 2.0 is not that far away (right?).

Re: Patch for Portland compiler support

On Nov 18, 2004, at 3:49 AM, Ralf Wildenhues wrote: I did [at least] one questionable thing: in the Linux linker section, I had to check for pgf77 or pgf90, because, contrary to the PG documentation, pgf77 and pgf90 need an additional "-fpic" in their linker command to create a shared library prop

RE: Using libtool 2.0 in autoconf tests

Sander Niemeijer wrote: > Hi, > > I have send this question to the list about a month ago, but > unfortunately, there hasn't been an answer yet, and the release of > libtool 2.0 is not that far away (right?). > > >

Wholes"ale Prices on Med`cine

Your favorite medcation --> 70% 0FF Sa1e (limitd. time only) VlAGRA from $63 VALlUM from $70 AMBlEN from $66 ClALlS from $90 XANX from $77 + MORE.. 0RDER NOW & GET SHlPPlNG AT N0 C0ST http://844.net.besentby.com ___ Libtool mailing list [EMAIL PROTECT

Get Meds Prescription Directly

Your favorite medcation - 70% 0FF Sa1e (limitd. time only) VlAGRA from $62 VAL1UM from $70 AMBlEN from $69 ClAL1S from $94 XANX from $71 + M0RE.. 0RDER NOW & GET SHIPPING AT N0 C0ST http://823.net.besentby.com ___ bug-lilypond mailing list [EMAIL PROT

Re: TODO

Bob Friesenhahn wrote: On Wed, 10 Nov 2004, Gary V. Vaughan wrote: It wouldn't be at all difficult to have 'libtoolize --ltdl --disable-nls' install a non-internationalised libltdl minus message catalogues into a parent package. But yes, we would have to take care to do it carefully. An improv

Re: Using libtool 2.0 in autoconf tests

* Sander Niemeijer wrote on Thu, Nov 18, 2004 at 01:54:12PM CET: > > I have send this question to the list about a month ago, but > unfortunately, there hasn't been an answer yet, and the release of > libtool 2.0 is not that far away (right?). Hmm. We need to at least wait for the copyright is