From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: Patch: f2c.h Question: objc backend
Date: Fri, 16 Jan 1998 01:51:00 -0000 [thread overview]
Message-ID: <rzqsoqp34rs.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <199801141754.KAA09862@jarvi.ezlink.com>
>>>>> "Trent" == Trent Jarvi <chaos@jarvi.ezlink.com> writes:
Trent> I noticed when porting the egcs rpm package to the alpha
Trent> machine that f2c.h was left out.
It should not be left out of gcc-lib/mumble/mumble/include.
Trent> When I mentioned to people that /usr/local/include/f2c.h was
Trent> left out I was informed that egcs was wrong. nothing should
Trent> go into /usr/local with prefix=/usr.
It's conditionally installed in $(includedir) IIRC, or at least it's
supposed to be. This is surely discussed in the g77 doc.
Trent> Christopher took the initiative to fix it. If its the wrong
Trent> fix we are interested in hearing so. I can imagine NFS setups
Trent> that the original would not be well suited for. The reason
Trent> f2c.h is being picked on is it is the only file in the egcs
Trent> package to go into /usr/local with prefix=/usr
The point is that we want to avoid losing on an incompatible f2c.h
that's already installed and picked up from $(includedir), which is
searched early. I think at one time the configure/instal procedure
tried to be clever and DTRT according to what was already installed.
This is only relevant if one compiles f2c-generated or f2c-compatible
C code subsequently for linking with g77 output.
I reckon an rpm should not install /usr/local/include/f2c.h but should
generate a conflict with one that's already there. Or something.
(I'm not an rpm expert.)
next prev parent reply other threads:[~1998-01-16 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-15 16:06 Trent Jarvi
1998-01-16 1:51 ` Dave Love [this message]
1998-01-17 1:40 ` Craig Burley
1998-01-19 2:45 ` Alexandre Oliva
1998-01-19 2:25 ` Craig Burley
1998-01-20 14:54 ` Dave Love
1998-01-19 2:45 ` Dave Love
-- strict thread matches above, loose matches on Subject: below --
1998-01-12 10:28 Christopher Seawood
1998-01-14 2:02 ` Dave Love
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=rzqsoqp34rs.fsf@djlvig.dl.ac.uk \
--to=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).