From: manfred@s-direktnet.de
To: egcs@cygnus.com
Subject: Re: [971031]: Fix for broken hypot funct. on m88k-motorola-sysv3
Date: Fri, 12 Dec 1997 01:46:00 -0000 [thread overview]
Message-ID: <9712120945.AA20731@lts.sel.alcatel.de> (raw)
In-Reply-To: <16860.881909814@hurl.cygnus.com>
On Thu, 11 December 1997, 23:56:54, law@cygnus.com wrote:
>
> In message <9711051320.AA18683@lts.sel.alcatel.de>you write:
> > Wed Nov 5 13:31:40 1997 Manfred Hollstein <manfred@s-direktnet.de>
> >
> > * fixincludes (str{len,spn,cspn} return value): Handle different
> > layout on sysV88.
> > (hypot): Provide a fake for hypot which is broken on m88k-motorola-sysv3.
> Thanks. I've installed this patch.
>
> However, is is really necessary to check the target system? Can't we just apply
> the fix regardless of the target?
Well, I added this for two reasons:
1. I didn't want to make changes which would probably affect other systems.
2. Some checks should be rewritten to use my new ${target...} stuff, because
building a cross compiler will otherwise fail to fix some header files;
most tests are like `if [ -f /vmunix ]...' which of course can be
misleading (or even wrong!) in a cross environment.
BTW: This patch has been obsoleted by the second part of
< http://www.cygnus.com/ml/egcs-bugs/1997-Dec/0137.html >
Manfred
next prev parent reply other threads:[~1997-12-12 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-04 23:44 egcs-971031: results on m88k-motorola-sysv3 haifa enabled manfred
1997-11-05 5:23 ` [971031]: Fix for broken hypot funct. on m88k-motorola-sysv3 manfred
1997-12-11 22:54 ` Jeffrey A Law
1997-12-12 1:46 ` manfred [this message]
1997-12-15 10:31 ` Jeffrey A Law
1997-12-15 13:11 ` Fixes for broken headers Bruce Korb
1997-12-18 12:29 ` Bruce Korb
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=9712120945.AA20731@lts.sel.alcatel.de \
--to=manfred@s-direktnet.de \
--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).