From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: libf2c/configure.in change
Date: Sun, 15 Feb 1998 11:33:00 -0000 [thread overview]
Message-ID: <rzq3ehk3e7d.fsf@djlvig.dl.ac.uk> (raw)
I didn't know the following libf2c change had gone in (good), but I
presume it should have a corresponding configure change.
Mon Jan 19 17:19:27 EST 1998
[...]
libi77: backspace.c: for b->ufmt==0, change sizeof(int) to
sizeof(uiolen). On machines where this would make a difference, it is
best for portability to compile libI77 with -DUIOLEN_int, which will
render the change invisible.
1998-02-15 Dave Love <d.love@dl.ac.uk>
* configure.in: Define UIOLEN_int per dmg advice for Jan 18
backspace.c change.
Index: configure.in
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/libf2c/configure.in,v
retrieving revision 1.2
diff -u -p -c -r1.2 configure.in
*** configure.in 1998/02/02 11:09:23 1.2
--- configure.in 1998/02/15 18:29:21
*************** F2C_INTEGER=$g77_cv_sys_f2cinteger
*** 286,291 ****
--- 286,297 ----
ac_cpp=$late_ac_cpp
AC_SUBST(F2C_INTEGER)
+ dnl Follow dmg advice to render 1998-01-19 change in backspace.c invisible.
+ if test "$F2C_INTEGER" = int; then
+ AC_DEFINE(UIOLEN_int) dnl 64-bit targets
+ else :
+ fi
+
AC_MSG_CHECKING(f2c long int type)
late_ac_cpp=$ac_cpp
ac_cpp="$late_ac_cpp -I$srcdir/../gcc/f -I../../gcc -I$srcdir/../gcc -I$srcdir/../gcc/config"
next reply other threads:[~1998-02-15 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-15 11:33 Dave Love [this message]
1998-02-15 20:19 ` Jeffrey A Law
1998-02-15 22:54 ` Toon Moene
1998-02-16 14:21 ` Dave Love
1998-02-17 23:59 ` Jeffrey A Law
1998-02-18 14:54 ` Craig Burley
1998-02-18 17:12 ` 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=rzq3ehk3e7d.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).