From: Ralf Baechle <ralf@oss.sgi.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: gcc include strangeness
Date: Sun, 10 Feb 2002 12:11:34 +0100 [thread overview]
Message-ID: <20020210121134.B2018@dea.linux-mips.net> (raw)
In-Reply-To: <20020209150155.GA853@paradigm.rfc822.org>; from flo@rfc822.org on Sat, Feb 09, 2002 at 04:01:55PM +0100
On Sat, Feb 09, 2002 at 04:01:55PM +0100, Florian Lohoff 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.
>
> Shouldnt sgidefs.h or its content be included in the gcc ?
There should be a copy of sgidefs.h in /usr/include rsp. for crosscompilers
in <prefix>/<target>/include/sgidefs.h. However the gcc varargs stuff
has been rewritten completely; the new implementation does no longer try
to include sgidefs.h.
Ralf
next prev parent reply other threads:[~2002-02-11 21:10 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 [this message]
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
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=20020210121134.B2018@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.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