From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: libf2c
Date: Mon, 16 Feb 1998 16:56:00 -0000 [thread overview]
Message-ID: <rzqk9avw5rq.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <2826.887589212@hurl.cygnus.com>
>>>>> "Jeff" == Jeffrey A Law <law@hurl.cygnus.com> writes:
>> Configuring in libraries/libf2c
>> loading site script /usr/local/share/config.site
>> loading cache /usr/local/var/config.cache
>> checking for gcc... (cached) gcc
Jeff> I suspect it's because either config.site or config.cache has a
Jeff> specification for what compiler to use...
Indeed, but it shouldn't be allowed to bite. (config.site is straight
from the autoconf manual, not that I think that DTRT; I think I
changed my former effort for purposes of testing like this.)
I followed the build process better this time :-). This is what the
old f/runtime used to do.
1998-02-16 Dave Love <d.love@dl.ac.uk>
* Makefile.in ($(CONFIGURE_TARGET_MODULES)): Run configure with
CONFIG_SITE=/dev/null to forestall lossage with site configuration.
Index: Makefile.in
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/Makefile.in,v
retrieving revision 1.14
diff -u -p -c -r1.14 Makefile.in
diff: conflicting specifications of output style
*** Makefile.in 1998/02/01 01:41:23 1.14
--- Makefile.in 1998/02/16 22:08:15
*************** $(CONFIGURE_TARGET_MODULES):
*** 1170,1180 ****
libsrcdir="$$s/$${dir}"; \
fi; \
if [ -f $${libsrcdir}/configure ] ; then \
! $(SHELL) $${libsrcdir}/configure \
$(CONFIG_ARGUMENTS) $${srcdiroption} \
--with-target-subdir="$(TARGET_SUBDIR)"; \
else \
! $(SHELL) $$s/configure \
$(CONFIG_ARGUMENTS) $${srcdiroption} \
--with-target-subdir="$(TARGET_SUBDIR)"; \
fi; \
--- 1170,1180 ----
libsrcdir="$$s/$${dir}"; \
fi; \
if [ -f $${libsrcdir}/configure ] ; then \
! CONFIG_SITE=/dev/null $(SHELL) $${libsrcdir}/configure \
$(CONFIG_ARGUMENTS) $${srcdiroption} \
--with-target-subdir="$(TARGET_SUBDIR)"; \
else \
! CONFIG_SITE=/dev/null $(SHELL) $$s/configure \
$(CONFIG_ARGUMENTS) $${srcdiroption} \
--with-target-subdir="$(TARGET_SUBDIR)"; \
fi; \
next prev parent reply other threads:[~1998-02-16 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-03 11:59 libf2c Dave Love
1998-02-03 21:34 ` libf2c Jeffrey A Law
1998-02-04 15:52 ` libf2c Dave Love
1998-02-11 18:20 ` libf2c Jeffrey A Law
1998-02-15 14:40 ` libf2c Dave Love
1998-02-15 16:32 ` libf2c Jeffrey A Law
1998-02-16 16:56 ` Dave Love [this message]
1998-02-18 1:53 ` libf2c Jeffrey A Law
1999-09-20 8:38 libf2c Christopher R. Jones
1999-09-30 18:02 ` libf2c Christopher R. Jones
1999-09-21 6:53 libf2c Christopher R. Jones
1999-09-30 18:02 ` libf2c Christopher R. Jones
1999-09-21 18:18 libf2c N8TM
1999-09-30 18:02 ` libf2c N8TM
1999-09-21 18:45 libf2c Christopher R. Jones
1999-09-30 18:02 ` libf2c Christopher R. Jones
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=rzqk9avw5rq.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).