From: Jeffrey A Law <law@cygnus.com>
To: Dave Love <d.love@dl.ac.uk>
Cc: egcs@cygnus.com
Subject: Re: libf2c FLAGS_TO_PASS [was Re: egcs-1.2 stuff ]
Date: Thu, 15 Apr 1999 21:42:00 -0000 [thread overview]
Message-ID: <19808.924237415@upchuck> (raw)
In-Reply-To: <rzq676y56m0.fsf@djlvig.dl.ac.uk>
In message < rzq676y56m0.fsf@djlvig.dl.ac.uk >you write:
> Jeff> I don't see any reason why libf2c should be using a different
> Jeff> quoting scheme than everything else. If it is, then we need to
> Jeff> find the reason why.
>
> There's a comment about it even in the context of the bogus patch. It
> may be ambiguous, but M-x occur easily finds the use to set shell
> variables (done for maintenance reasons); at the moment I don't see
> any need to change that.
Yea. I'll note that libchill handles this by doing CC='$(CC)' and similarly
for other variables instead of using FLAGS_TO_PASS in the config.status rule.
libiberty does nothing to pass CC and friends around when running config.status
libobjc works like libchill.
I think cleaning up this *(@#$ mess ought to be put on the configure/makefile
rewrite list. Having every runtime library do things a little differently
is just plain dumb.
> Jeff> If we ever made libf2c's testsuite
>
> It doesn't have one AFAIK, and I'm not sure it would make sense
> separately. Regardless, it isn't necessary to understand dejagnu to
> solve the problem at hand.
Sure it makes sense. There's no reason we can't build a dejagnu testsuite
for libf2c just like we've started doing for libstdc++, libio & libg++.
> Jeff> work work like the rest, then RUNTESTFLAGS would become highly
> Jeff> relevant.
>
> The remaking stuff in libf2c has broken anyway, making maintenance a
> pain, but I don't think it has to be made worse.
I don't think that RUNTESTFLAGS is particularly important for the rebuilding
of config.status. But I don't see the benefit of taking it out. Every
runtime should pass the same set of flags around in the long term. Anything
else is dumb.
In fact, I might claim that we should have a single template Makefile and
configury the runtimes and the runtimes should simply plug in a set of subdirs
to build, the sources and library name. The way we're doing things now is far
from maintainable in the long term.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: Dave Love <d.love@dl.ac.uk>
Cc: egcs@cygnus.com
Subject: Re: libf2c FLAGS_TO_PASS [was Re: egcs-1.2 stuff ]
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <19808.924237415@upchuck> (raw)
Message-ID: <19990430231500.c0cE7jjqmMYZRrbJHlDxUM9ajptQVLu8Xb2DWMb_Gdk@z> (raw)
In-Reply-To: <rzq676y56m0.fsf@djlvig.dl.ac.uk>
In message < rzq676y56m0.fsf@djlvig.dl.ac.uk >you write:
> Jeff> I don't see any reason why libf2c should be using a different
> Jeff> quoting scheme than everything else. If it is, then we need to
> Jeff> find the reason why.
>
> There's a comment about it even in the context of the bogus patch. It
> may be ambiguous, but M-x occur easily finds the use to set shell
> variables (done for maintenance reasons); at the moment I don't see
> any need to change that.
Yea. I'll note that libchill handles this by doing CC='$(CC)' and similarly
for other variables instead of using FLAGS_TO_PASS in the config.status rule.
libiberty does nothing to pass CC and friends around when running config.status
libobjc works like libchill.
I think cleaning up this *(@#$ mess ought to be put on the configure/makefile
rewrite list. Having every runtime library do things a little differently
is just plain dumb.
> Jeff> If we ever made libf2c's testsuite
>
> It doesn't have one AFAIK, and I'm not sure it would make sense
> separately. Regardless, it isn't necessary to understand dejagnu to
> solve the problem at hand.
Sure it makes sense. There's no reason we can't build a dejagnu testsuite
for libf2c just like we've started doing for libstdc++, libio & libg++.
> Jeff> work work like the rest, then RUNTESTFLAGS would become highly
> Jeff> relevant.
>
> The remaking stuff in libf2c has broken anyway, making maintenance a
> pain, but I don't think it has to be made worse.
I don't think that RUNTESTFLAGS is particularly important for the rebuilding
of config.status. But I don't see the benefit of taking it out. Every
runtime should pass the same set of flags around in the long term. Anything
else is dumb.
In fact, I might claim that we should have a single template Makefile and
configury the runtimes and the runtimes should simply plug in a set of subdirs
to build, the sources and library name. The way we're doing things now is far
from maintainable in the long term.
jeff
next prev parent reply other threads:[~1999-04-15 21:42 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-19 1:37 egcs-1.2 stuff Jeffrey A Law
[not found] ` < 19506.921836210@hurl.cygnus.com >
1999-03-19 8:49 ` H.J. Lu
[not found] ` < m10O2Sm-000ErMC@ocean.lucon.org >
1999-03-19 8:56 ` Jeffrey A Law
[not found] ` < 20206.921862608@hurl.cygnus.com >
1999-03-19 9:06 ` H.J. Lu
[not found] ` < m10O2ic-000ErMC@ocean.lucon.org >
1999-03-19 9:14 ` Jeffrey A Law
[not found] ` < 20303.921863639@hurl.cygnus.com >
1999-03-19 16:31 ` H.J. Lu
1999-03-31 23:46 ` H.J. Lu
1999-04-03 20:37 ` Jeffrey A Law
1999-04-03 22:42 ` H.J. Lu
1999-04-30 23:15 ` H.J. Lu
1999-04-30 23:15 ` Jeffrey A Law
1999-04-03 20:52 ` Jeffrey A Law
1999-04-03 22:39 ` H.J. Lu
1999-04-03 23:41 ` Jeffrey A Law
1999-04-04 8:49 ` H.J. Lu
1999-04-12 2:55 ` Jeffrey A Law
1999-04-12 8:50 ` H.J. Lu
1999-04-30 23:15 ` H.J. Lu
1999-04-12 9:35 ` H.J. Lu
1999-04-12 10:18 ` craig
1999-04-12 10:34 ` Zack Weinberg
1999-04-12 19:17 ` craig
1999-04-12 19:26 ` Zack Weinberg
1999-04-12 23:10 ` H.J. Lu
1999-04-30 23:15 ` H.J. Lu
1999-04-13 5:03 ` craig
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` Zack Weinberg
1999-04-13 21:24 ` libf2c FLAGS_TO_PASS [was Re: egcs-1.2 stuff ] Jeffrey A Law
1999-04-14 8:19 ` H.J. Lu
1999-04-30 23:15 ` H.J. Lu
1999-04-14 13:25 ` Dave Love
1999-04-14 13:50 ` Jeffrey A Law
1999-04-15 6:57 ` Dave Love
1999-04-15 21:42 ` Jeffrey A Law [this message]
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Dave Love
1999-04-15 7:09 ` craig
1999-04-15 21:53 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` Dave Love
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` egcs-1.2 stuff craig
1999-04-30 23:15 ` Zack Weinberg
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` H.J. Lu
1999-04-12 10:06 ` H.J. Lu
1999-04-12 13:29 ` Jeffrey A Law
1999-04-12 13:36 ` H.J. Lu
1999-04-12 22:13 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` H.J. Lu
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` H.J. Lu
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` H.J. Lu
1999-04-30 23:15 ` Jeffrey A Law
1999-04-30 23:15 ` H.J. Lu
1999-04-30 23:15 ` Jeffrey A Law
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` H.J. Lu
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` H.J. Lu
1999-03-19 10:26 ` Franz Sirl
1999-03-31 23:46 ` Franz Sirl
1999-03-19 13:39 ` Donn Terry
[not found] ` < 36F2C319.949610F6@interix.com >
1999-03-19 23:43 ` Jeffrey A Law
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Donn Terry
1999-03-24 14:05 ` Toon Moene
[not found] ` < 36F95EEA.F12F4575@moene.indiv.nluug.nl >
1999-03-24 18:49 ` craig
1999-03-25 13:11 ` Toon Moene
1999-03-31 23:46 ` Toon Moene
1999-03-31 23:46 ` craig
1999-03-25 14:21 ` Richard Henderson
1999-03-26 6:55 ` Toon Moene
1999-03-31 23:46 ` Toon Moene
1999-03-31 23:46 ` Richard Henderson
1999-03-31 23:46 ` Toon Moene
1999-03-31 23:46 ` Jeffrey A Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19808.924237415@upchuck \
--to=law@cygnus.com \
--cc=d.love@dl.ac.uk \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).