From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Florian Lohoff <flo@rfc822.org>, linux-mips@oss.sgi.com
Subject: Re: gcc include strangeness
Date: Mon, 11 Feb 2002 23:04:27 +0100 [thread overview]
Message-ID: <20020211230427.D4623@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.GSO.3.96.1020211134516.18917A-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Feb 11, 2002 at 01:51:47PM +0100
On Mon, Feb 11, 2002 at 01:51:47PM +0100, Maciej W. Rozycki wrote:
> > i just stumbled when i tried to compile a program (bootloader) with
> > gcc which uses varargs. I got the error that "sgidefs.h" was missing.
> > sgidefs.h is contained in the glibc which gets included by va-mips.h
> > from stdarg.h - I dont think this is correct as i should be able
> > to compile programs without glibc.
>
> Hmm, in 2.95.3 in va-mips.h I see:
>
> /* Get definitions for _MIPS_SIM_ABI64 etc. */
> #ifdef _MIPS_SIM
> #include <sgidefs.h>
> #endif
>
> so you shouldn't need sgidefs.h normally. Or did something get broken for
> 3.x?
Gcc is supposed to define _MIPS_SIM.
Ralf
prev parent reply other threads:[~2002-02-11 23:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 15:01 gcc include strangeness Florian Lohoff
2002-02-10 11:11 ` Ralf Baechle
2002-02-12 11:49 ` Maciej W. Rozycki
2002-02-11 12:51 ` Maciej W. Rozycki
2002-02-11 13:53 ` Florian Lohoff
2002-02-11 14:15 ` Maciej W. Rozycki
2002-02-11 14:27 ` Johannes Stezenbach
2002-02-11 15:10 ` Maciej W. Rozycki
2002-02-11 16:28 ` Johannes Stezenbach
2002-02-11 17:06 ` Maciej W. Rozycki
2002-02-11 22:20 ` Ralf Baechle
2002-02-12 15:55 ` Dominic Sweetman
2002-02-12 15:55 ` Dominic Sweetman
2002-02-12 17:08 ` Brian Murphy
2002-02-12 17:20 ` Timothy Daly
2002-02-11 22:07 ` Ralf Baechle
2002-02-11 22:07 ` Ralf Baechle
2002-02-11 15:37 ` Florian Lohoff
2002-02-11 16:53 ` Johannes Stezenbach
2002-02-11 17:08 ` Guido Guenther
2002-02-11 22:04 ` Ralf Baechle [this message]
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=20020211230427.D4623@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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