Re: Improve handling of option abbreviations in config.status

Hi, On Wed, May 11, 2005 at 12:24:35PM -0700, Paul Eggert wrote: Stepan Kasal [EMAIL PROTECTED] writes: I noticed that --debug and --version were handled differently than other config.status options. Is there a reason for this? ... please install your change. Done. Stepan

g95 is not gfortran

There are two GNU fortran projects that use names g95 (g95.sf.net) and gfortran. I am using g95 right now and it seems to be more ready that gfortran. So any chance of including it in the list of compilers? juha Index: fortran.m4

using target-specific variables?

Hi folks, How can I use target-specific variables in Makefiles generated by Automake? My Makefile.am says something like lib_LIBRARIES = libmylib.a libmylib_gcc3.a libmylib_a_SOURCES = foo.c bar.c libmylib_gcc3_a_SOURCES = $(libmylib_a_SOURCES)

Re: using target-specific variables?

Hi Harald, * Harald Dunkel wrote on Thu, May 12, 2005 at 10:45:40AM CEST: How can I use target-specific variables in Makefiles generated by Automake? In general, that is not possible. For specific variables, like CFLAGS, CPPFLAGS, you may do this by using target_CFLAGS = ... My

Re: using target-specific variables?

Ralf Wildenhues wrote: Hi Harald, * Harald Dunkel wrote on Thu, May 12, 2005 at 10:45:40AM CEST: How can I use target-specific variables in Makefiles generated by Automake? In general, that is not possible. For specific variables, like CFLAGS, CPPFLAGS, you may do this by using

Re: using target-specific variables?

Hi Harald, * Harald Dunkel wrote on Thu, May 12, 2005 at 01:43:51PM CEST: Ralf Wildenhues wrote: * Harald Dunkel wrote on Thu, May 12, 2005 at 10:45:40AM CEST: How can I use target-specific variables in Makefiles generated by Automake? In general, that is not possible. For specific

Re: using target-specific variables?

Hello, On Thu, May 12, 2005 at 02:02:54PM +0200, Ralf Wildenhues wrote: * Harald Dunkel wrote on Thu, May 12, 2005 at 01:43:51PM CEST: Anyway, if I introduce a line myexe: some_internal_tool_used_at_build_time then Automake shows the same misbehaviour: It assumes that I would

Re: AC_CHECK_SIZEOF for members

Paul Eggert wrote: Sam Steingold [EMAIL PROTECTED] writes: [...] the reason I want a CPP macro and not a run-time if is that the code will end up looking like this: if (size_of(u.ut_tv.tv_sec) = 4) a_function_expecting_32_bit_argument(u.ut_tv.tv_sec); else

Re: using target-specific variables?

* Stepan Kasal wrote on Thu, May 12, 2005 at 02:57:46PM CEST: On Thu, May 12, 2005 at 02:02:54PM +0200, Ralf Wildenhues wrote: * Harald Dunkel wrote on Thu, May 12, 2005 at 01:43:51PM CEST: Anyway, if I introduce a line myexe: some_internal_tool_used_at_build_time then

Re: AC_CHECK_SIZEOF for members

* Allan Clark [EMAIL PROTECTED] [2005-05-12 17:15:49 +0800]: Paul Eggert wrote: Sam Steingold [EMAIL PROTECTED] writes: [...] the reason I want a CPP macro and not a run-time if is that the code will end up looking like this: if (size_of(u.ut_tv.tv_sec) = 4)