Re: substitution

2000-07-18 Thread Tom Tromey
Jerome> I try to write a transportable AC_DEFUN: Jerome> I want to wrire simple substitution command as (in bash): Jerome> $bb=${BB%%.*} Jerome> Is there a more transportable way to do that ? This is more of an autoconf question. Generally the answer is "use sed". Do you really mean to assign t

substitution

2000-07-18 Thread Jerome G. Benoit
I try to write a transportable AC_DEFUN: I want to wrire simple substitution command as (in bash): $bb=${BB%%.*} This works on some machine, but on my Solaris station I get the message: bad substitution Is there a more transportable way to do that ? thanks in advance, Jerome BENOIT

Re: -c -o

2000-07-18 Thread Peter Eisentraut
Akim Demaille writes: > But precisely because of your needs, don't you need an output variable > or something instead of the CPP symbol? Certainly so. -- Peter Eisentraut Sernanders väg 10:115 [EMAIL PROTECTED] 75262 Uppsala http://yi.org/peter-e/

Re: Fortran dependency tracking

2000-07-18 Thread Tom Tromey
Martin> I understand you're trying to get a new release out. It isn't that. It's just that I (and, apparently, the other automake hackers) have very little time. Tom

Re: Fortran dependency tracking

2000-07-18 Thread Martin Wilck
Dear Tom Tromey, you wrote on Today: > You might be in for a long wait, sorry. I understand you're trying to get a new release out. I certainly don't want to interfere with that, nor put any sort of pressure upon you or other maintainers. At present I'd mainly like to know - if these fetaures a

Re: Fortran dependency tracking

2000-07-18 Thread Tom Tromey
Martin> Last comment: If some day my Fortran/cpp patches get accepted Martin> in some form for the autotools (btw: I'd appreciate some Martin> feedback from the automake maintainers on the patch I Martin> suggested) You might be in for a long wait, sorry. Tom

Re: Fortran dependency tracking

2000-07-18 Thread Martin Wilck
Dear Tom Tromey, you wrote on Today: > We already handle this for C compilers. It just means writing a lot > of cases. Fine, but as I said, for 9 out of 10 compilers users would see the message: Checking for dependency style of f77 ... none which is probably not what we want. > Don't let me

Re: [patch] DESTDIR support for cpio

2000-07-18 Thread Tom Tromey
> "Tim" == Tim Heath <[EMAIL PROTECTED]> writes: Tim> I am interested in combining libraries created in a deep project Tim> into one library instead of a bunch of little ones. How can this Tim> be accomplished? Use libtool convenience libraries for the subdirectories, and combine them into

Re: Fortran dependency tracking

2000-07-18 Thread Akim Demaille
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: Tom> Also, writing a dependency tool in a portable way seems hard. In particular if you consider the lexical flexibility of Fortran. It is reasonable to require a particular form of include/INCLUDE etc. from the maintainers who are making th

Re: automake vs. autoconf 2.14a

2000-07-18 Thread Johan Danielsson
Akim Demaille <[EMAIL PROTECTED]> writes: > What kind of warnings are you referring to? I tried on a couple of > packages and didn't find many related to Automake. AC_OUTPUT_COMMANDS and friends, AC_CHECK_TOOL_PREFIX, AC_LANG_SAVE, AC_DECL_YYTEXT. /Johan

Re: automake vs. autoconf 2.14a

2000-07-18 Thread Akim Demaille
> "Johan" == Johan Danielsson <[EMAIL PROTECTED]> writes: Johan> What's the deal? If you run autoconf -W obsolete you get a Johan> bunch of warnings for automake stuff. The objective is to release the next Automake independently of the changes in Autoconf, so that people are not obliged to u

Re: [patch] DESTDIR support for cpio

2000-07-18 Thread Tim Heath
I am interested in combining libraries created in a deep project into one library instead of a bunch of little ones. How can this be accomplished? Thanks, Tim Heath Alain Magloire wrote: > > > > > [This message has also been posted.] > > This patch adds support to cpio 2.4.2 for the DESTDIR m

Re: Fortran dependency tracking

2000-07-18 Thread Tom Tromey
Martin> Wrt to supporting every compiler, let's forget about it. So Martin> far I haven't seen a single compiler with decent dependency Martin> tracking support. And even if they did, you can be certain Martin> that each and every one would use a different option syntax Martin> and output format.

automake vs. autoconf 2.14a

2000-07-18 Thread Johan Danielsson
What's the deal? If you run autoconf -W obsolete you get a bunch of warnings for automake stuff. /Johan

Re: Fortran dependency tracking

2000-07-18 Thread Martin Wilck
Dear Tom Tromey, you wrote on Yesterday: > Actually, ideally we'd like to support every compiler. However, I > think we'd also rather avoid distributing a complete Fortran > dependency-finding tool with every Fortran-using package. This is > hardly ideal, I guess. Wrt to supporting every compi

Re: -c -o

2000-07-18 Thread Akim Demaille
> "Peter" == Peter Eisentraut <[EMAIL PROTECTED]> writes: Peter> If I'm redefining the .c => .o pattern rule for my purposes Peter> (e.g., dependency generation) then I need to know whether the Peter> compiler supports -c -o, otherwise I have to do something like Peter> cc && mv. Please keep