autoconf 2.49a / Sun WorkShop C/C++

Hi, There used to be a bug in autoconf 2.13 related to the generation of dependencies using the C/C++ compiler. This bug is still there in autoconf 2.49a. I am using the example project below: http://www.murrayc.com/learning/linux/automake/helloworld_cc-0.2.tar.gz The Sun WorkShop C/C++

Re: autoconf 2.49a / Sun WorkShop C/C++

On Sep 12, 2000, Dimitri PAPADOPOULOS-ORFANOS [EMAIL PROTECTED] wrote: There used to be a bug in autoconf 2.13 related to the generation of dependencies using the C/C++ compiler. This bug is still there in autoconf 2.49a. autoconf has nothing to do with this. It is automake that introduces

Should the C++ sourcefile extension be changed?

Hi, I see there was a suggestion to change the extension for C++ sourcecode files a couple of months ago. Someone had tested the .cxx extension and found it to work with all compilers he could lay his hands on (quite a few on UNIX systems, plus at least MSVisualC++ on MSWindows). So, as the

Re: [autoconf-patches] _AC_OUTPUT_SUBDIRS: check for configure.gnu as well [Resend]

On Sep 12, 2000, Akim Demaille [EMAIL PROTECTED] wrote: Alternatively (sorry for insisting but your proposal seems a bit too ``specific'' to get into Autoconf per se), can't you just run Configure with AC_CONFIG_SUBDIRS(my/autoconfed/dir1 my/autoconfed/dir2)

FYI: autoupdate-gnu-sed [Was: Autoupdate test failing on Solaris7]

I just committed this: Index: ChangeLog from Akim Demaille [EMAIL PROTECTED] * autoupdate.sh (sed): Look for GNU sed. (usage): Ask for GNU sed. Index: autoupdate.sh === RCS file: /cvs/autoconf/autoupdate.sh,v

RE: Autoupdate test failing on Solaris7

-Original Message- From: Akim Demaille [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 12, 2000 12:11 PM To: Bernard Dautrevaux Cc: Autoconf mailing list (Adresse de messagerie) Subject: Re: Autoupdate test failing on Solaris7 "Bernard" == Bernard Dautrevaux [EMAIL

Re: [autoconf-patches] _AC_OUTPUT_SUBDIRS: check for configure.gnu as well

Hi! --[Akim Demaille]--[EMAIL PROTECTED] "diger" == diger Kuhlmann R writes: Well... I don't have to tell you what I think about "Gnus"... Still, why don't you want both Configure and configure in the same dir? Are you using a case insensitive FS? AmigaOS filesystems are traditionally

Fwd: Re: I'm new in cygwin: how to mmap?

FYI on portability issue. Cheers, Earnie. Note: forwarded message attached. __ Do You Yahoo!? Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ Hi! "Dr. Volker Zell" [EMAIL PROTECTED] wrote: "Corinna" == Corinna

RE: autoupdate-gnu-sed [Was: Autoupdate test failing on Solaris7]

-Original Message- From: Akim Demaille [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 12, 2000 2:49 PM To: Bernard Dautrevaux Cc: Autoconf mailing list (Adresse de messagerie) Subject: FYI: autoupdate-gnu-sed [Was: Autoupdate test failing on Solaris7] I just committed

Re: autoupdate-gnu-sed [Was: Autoupdate test failing on Solaris7]

"Bernard" == Bernard Dautrevaux [EMAIL PROTECTED] writes: Bernard Fine for me, although I wonder why you insist at eliminating Bernard the "-e" sed options when there is only one sed command; I Bernard know in this case thay may be omitted, but I usually keep Bernard them for consistency with

Re: [autoconf-patches] _AC_OUTPUT_SUBDIRS: check for configure.gnu as well [Resend]

"Akim" == Akim Demaille [EMAIL PROTECTED] writes: Akim Alternatively (sorry for insisting but your proposal seems a bit Akim too ``specific'' to get into Autoconf per se), can't you just Akim run Configure with Akim AC_CONFIG_SUBDIRS(my/autoconfed/dir1 my/autoconfed/dir2) Akim

Re: Should the C++ sourcefile extension be changed?

Hello, Morten! So, as the current extension (.cc) _really_ confuses MSVisualC++, it'd be nice if the patch below is applied before releasing v2.50. I remember hearing about the problem that M$VC and some Macintosh C++ compiler don't support _any_ common C++ extention by default. Indeed,

Re: Should the C++ sourcefile extension be changed?

On Tue, Sep 12, 2000 at 01:01:09PM -0400, Pavel Roskin wrote: I believe it would be more constructive to make M$VC accept .cc extention is some non-interactive way. Anybody knows how? $(CP) foo.cc foo.cpp $(CC) foo.cpp ? mrc -- Mike Castle Life is like a clock: You can work

Re: Should the C++ sourcefile extension be changed?

Hello! On Tue, 12 Sep 2000, Mike Castle wrote: On Tue, Sep 12, 2000 at 01:01:09PM -0400, Pavel Roskin wrote: I believe it would be more constructive to make M$VC accept .cc extention is some non-interactive way. Anybody knows how? $(CP) foo.cc foo.cpp $(CC) foo.cpp This should be the

Re: Blind fix for wierd test ordering in configure

On Tue, Sep 12, 2000 at 01:32:07AM -0300, Alexandre Oliva wrote: On Sep 11, 2000, "Gary V. Vaughan" [EMAIL PROTECTED] wrote: I don't actually see the point of making AC_PROG_LIBTOOL require _AC_PROG_LIBTOOL, so I figured I must be missing something... The point is to avoid duplicate

Re: HTML format documentation

Yes, thank you, I know this. This is what I do. But pardon me, this is by no means something I consider ``natural''. I said this is the natural way to "follow the spec". Whether it seems entirely natural as a way to do the job is not the question. We are not going to change the

Re: HTML format documentation

Richard Stallman [EMAIL PROTECTED] writes: CC=sun4-cc ./configure Hence, next time configure is run, it forgets about the CC which was used to build config.cache, and you get an inconsistent system. So configure needs the user to tell things instead of doing stuff in