From: hjl@lucon.org (H.J. Lu)
To: law@cygnus.com
Cc: teunis@mauve.computersupportcentre.com, egcs@cygnus.com,
drepper@gnu.ai.mit.edu (Ulrich Drepper)
Subject: Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
Date: Mon, 17 Nov 1997 10:23:00 -0000 [thread overview]
Message-ID: <m0xXVor-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: <10207.879749319@hurl.cygnus.com>
>
> In message < Pine.LNX.3.96.971114180852.16600A-100000@sigil.computersupportcentre.com >you write:
> > and:
> > What's the proper way to test egcs? (make check?)
> make check
>
> > How does one make a cross-compiler?
> > (first few attempts failed ....)
> Same, however you need many more pieces to get meaningful results (cross
> assembler, linker, libraries & a simulator).
>
>
> > ../streambuf.h:394: warning: invalid type `void *' for default argument to ios *'
> > In file included from ./../tests/hounddog.cc:25:
> > ../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
> > ../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
> > ../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
> Hmmm, I thought we had fixed this problem several snapshots ago.
>
> Jason, HJ any thoughts?
>
I think it may be NULL defined in the kernel source. Jason has defined
NULL in _G_config.h. But glibc uses its own _G_config.h. Ulrich may
be glibc should do the same. Should it be in glibc 2.0.6?
--
H.J. Lu (hjl@gnu.ai.mit.edu)
next prev parent reply other threads:[~1997-11-17 10:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-14 17:02 teunis
1997-11-16 22:46 ` Jeffrey A Law
1997-11-17 10:23 ` H.J. Lu [this message]
1997-11-17 13:18 ` Paul Koning
1997-11-17 14:21 ` teunis
1997-11-18 22:06 ` Jeffrey A Law
1997-11-19 8:46 ` teunis
1997-11-22 0:42 ` Jeffrey A Law
1997-11-23 15:41 ` Joel Sherrill
1997-11-24 0:32 ` Jeffrey A Law
1997-11-27 2:29 ` teunis
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=m0xXVor-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@gnu.ai.mit.edu \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=teunis@mauve.computersupportcentre.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).