From: Chip Salzenberg <chip@rio.atlantic.net>
To: egcs@cygnus.com
Subject: libg++?
Date: Sat, 30 Aug 1997 11:27:45 -0000 [thread overview]
Message-ID: <199708301342.JAA07516@rio.atlantic.net> (raw)
Could someone please explain the relationships among libio, libstd++, and
libg++? And given all the activity in C++, could someone explain why
libg++ hasn't been modified since 14 February 1997 (version 2.8.0b6)?
--
Chip Salzenberg - a.k.a. -
(Roller coaster on camera:) "Wow, this square quarter mile
has unbelievably good light rail transit!" // MST3K
WARNING: multiple messages have this Message-ID
From: Derek Wildstar <dwild@nin.org>
To: egcs@cygnus.com
Subject: egcs v970828 builds fine on linux-i586libc1 =)
Date: Sat, 30 Aug 1997 12:00:09 -0000 [thread overview]
Message-ID: <199708301342.JAA07516@rio.atlantic.net> (raw)
Message-ID: <19970830120009.7xYq36hwptoEukA-kVD56R0oUGA3gjXFrJNZewqrI30@z> (raw)
Built the whole dist with CFLAGS='-O6 -mpentium -pipe' CXXFLAGS='-O6 -mpentium
-pipe' LDFLAGS='-m486 -s -Xlinker -n'....the whole package built fine. I then
went into the gcc dir and built stage1, stage2, stage3 in the normal fashion
to test the compiler. Everything appears to be working, even with '-O6
-mpentium'.
On a side note, it may be worth mentioning that XFree86 should _not_ be built
with -O6. The package builds, but some strange runtime problems pop up...the
most annoying of which is a keyboard mapping problem that causes certain keys
to send characters when they are released instead of when they are pressed.
After rebuilding the package with -O2 the problems went away. (not saying
this is a compiler problem, just for your reference if you end up building X
;)
The last thing...honest...I was just wondering how up-to-date the
pentium-specific stuff is in egcs (ie if i have 970828, is this reasonably
close to 970821+the pcgg patch) Since i'm in a pretty good position to
break^H^H^H^H^Htest this stuff on my own system, i'd like to stay as current
as possible. Going to attempt a couple egcs cross-compiler builds when I get
the time, i'll let you know how things go (ix86-linux->sparc-sunos4.1.4 and
ix86-linux->sparc-linux), and send fixes if i run into any trouble.
keep up the good work =)
--
Joel Boring (aka Derek Wildstar) Eskimo North
dwild@eskimo.com, DWildstar@IRC Seattle, WA
IRC Admin / Assistant Sysadmin / Tech Support (206) 361-1161
WARNING: multiple messages have this Message-ID
From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: libI77 fmt uncleanliness
Date: Sat, 30 Aug 1997 12:00:09 -0000 [thread overview]
Message-ID: <199708301342.JAA07516@rio.atlantic.net> (raw)
Message-ID: <19970830120009.k1ojE6BVfIBUtTSGVOD2EzEFolu8JqKM9b1AZPw9wcI@z> (raw)
In-Reply-To: Fri, 29 Aug 1997 22:06:24 -0700"
>>>>> "Richard" == Richard Henderson writes:
Richard> I77's fmt.h defines struct syl as
Richard> struct syl { int op, p1, p2, p3; }
Richard> and then goes off and does things like
Richard> *(char **)&sp->p2 = s + 1;
Richard> which is broken for 64-bit hosts.
We normally pass on basic problems with libf2c exposed by g77 use to
the excellent f2c maintainer so I've done that for comment. (I don't
think the g77 frontend has any knowledge of such things; burley
probably can't currently read this due to the GNU notwork.)
next reply other threads:[~1997-08-30 11:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-30 11:27 Chip Salzenberg [this message]
1997-08-30 12:00 ` libI77 fmt uncleanliness Dave Love
1997-08-30 12:00 ` egcs v970828 builds fine on linux-i586libc1 =) Derek Wildstar
1997-08-30 12:00 Incorrect i960 linker config Stephen Williams
1997-08-30 21:24 ` libg++? Jason Merrill
1997-08-30 22:12 egcs-970828 install Weiwen Liu
1997-08-30 22:12 ` libg++? Joe Buck
1997-12-02 9:23 libg++ Lee Iverson
1997-12-02 13:14 ` libg++ Mumit Khan
1997-12-02 18:18 ` libg++ H.J. Lu
1998-01-20 14:54 libg++ Oleg Krivosheev
1998-01-23 11:15 ` libg++ H.J. Lu
1998-06-29 23:55 libg++ Daniel Bernstein
1998-06-30 11:53 ` libg++ H.J. Lu
1998-06-30 14:08 ` libg++ Manfred Hollstein
[not found] <Pine.SUN.3.95-heb-2.07.980629191358.564A-100000.cygnus.egcs@beitza.jct.ac.il>
1998-06-30 19:49 ` libg++ Nathan Myers
1998-07-01 7:26 ` libg++ H.J. Lu
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=199708301342.JAA07516@rio.atlantic.net \
--to=chip@rio.atlantic.net \
--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).