From: J. Kean Johnston <jkj@sco.com>
To: egcs@cygnus.com
Subject: Much c-torture success on 970825 :-)
Date: Tue, 26 Aug 1997 01:43:01 -0000 [thread overview]
Message-ID: <199708260143.SAA04797@cygnus.com> (raw)
Hi again.
On SCO Open Server 5.0, in both COFF and ELF modes, egcs 970825 passes
c-torture with flying colours. It only has a single expected failure.
I am about to do all of the libg++ tests, and will keep you all informed
of success on that front.
Also of interest, it is currently building cleanly on SCO UnixWare SVR5.
This is a HUGE win for the EGCS project. Well done everyone, this is
great. Just for the sake of satisfying my perverse curiosity, I am
going to try and build XFree86 3.3.1 with the newly built, fresh out
of the box egcs, and see what happens.
JKJ
WARNING: multiple messages have this Message-ID
From: Jim Wilson <wilson@cygnus.com>
To: egcs@cygnus.com
Subject: Re: 970825 Snapshot Available
Date: Tue, 26 Aug 1997 01:43:01 -0000 [thread overview]
Message-ID: <199708260143.SAA04797@cygnus.com> (raw)
Message-ID: <19970826014301.ceBKep2O7ztJSAnY_JGUltopgvR3JCMAXmCzHL2XJio@z> (raw)
In-Reply-To: 970825 Snapshot Available
What happened to my SMP patch?
There have so many people reporting bugs, submitting patches, etc, that it has
been impossible to handle them all in a timely fashion. I expect that things
will get better soon, once we get past the initial surge caused by the project
startup. There is also the problem that I am new at this, and still trying
to figure out how to deal with all of the email, prioritize work, etc.
So far, I have been concentrating on the build problems. I wanted to get
as many as possible of the serious build problems fixed early, so that more
people would be able to try egcs. This is also important since we are
planning on making an initial release sometime within the next few weeks.
I just today started looking at the various patches that have been submitted
since the project started.
I am already working on your SMP patch. I expect to check it in today
unchanged. My only comment is to notice that the f/runtime Makefile is
missing dependencies. If one of the lib*77 libraries is updated, libf2c.a
won't be updated. There were some partial dependencies for this before your
change, but they were flawed, so I does appear that they should be removed.
Still, it seems that this should be fixed someday.
The build cannot be done without it on an SMP machine.
I wasn't aware of that. I thought it was a problem only if you used the
-j option. If -jN N!=1 is the default, can't you simply work around this
by using -j1?
Jim
WARNING: multiple messages have this Message-ID
From: J. Kean Johnston <jkj@sco.com>
To: egcs@cygnus.com
Subject: libf2c.a doesnt obey MULTILIB
Date: Tue, 26 Aug 1997 01:43:01 -0000 [thread overview]
Message-ID: <199708260143.SAA04797@cygnus.com> (raw)
Message-ID: <19970826014301.-6DUWj5G6fG0-QcT8c89s4-u4AnpWio5zEKQz_1OQAM@z> (raw)
Hi all.
Not sure if this is a known problem or not, but when building g77, it
does not obey the multilib rules when building libf2c.a. I am
assuming it should.
JKJ
next reply other threads:[~1997-08-26 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-26 1:43 J. Kean Johnston [this message]
1997-08-26 1:43 ` 970825 Snapshot Available Jim Wilson
1997-08-26 1:43 ` libf2c.a doesnt obey MULTILIB J. Kean Johnston
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=199708260143.SAA04797@cygnus.com \
--to=jkj@sco.com \
--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).