From: NightStrike <nightstrike@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: More questions on sysroots
Date: Sat, 22 Dec 2007 17:54:00 -0000 [thread overview]
Message-ID: <b609cb3b0712220954i1a5df03fs6d84903bd9b8124f@mail.gmail.com> (raw)
In-Reply-To: <476D4D46.260ECF52@dessent.net>
On 12/22/07, Brian Dessent <brian@dessent.net> wrote:
> NightStrike wrote:
>
> > This is where it dies as follows:
> > In file included from ../../../gcc/libgcc/../gcc/libgcc2.c:33:
> > ../../../gcc/libgcc/../gcc/tsystem.h:90:19: error: stdio.h: No such
> > file or directory
> > ../../../gcc/libgcc/../gcc/tsystem.h:93:23: error: sys/types.h: No
> > such file or directory
> > ../../../gcc/libgcc/../gcc/tsystem.h:96:19: error: errno.h: No such
> > file or directory
> > ../../../gcc/libgcc/../gcc/tsystem.h:103:20: error: string.h: No such
> > file or directory
> > ../../../gcc/libgcc/../gcc/tsystem.h:104:20: error: stdlib.h: No such
> > file or directory
> > ../../../gcc/libgcc/../gcc/tsystem.h:105:20: error: unistd.h: No such
> > file or directory
>
> You cut out the part that would have been useful, namely the -B and -I
> arguments passed to xgcc.
Not really cut out.. I just redirected stdout to /dev/null and only
had the stderr to look at. Here is the part that I lost:
/var/tmp/build/gcc-svn/build-x86_64-pc-linux/./gcc/xgcc
-B/var/tmp/build/gcc-svn/build-x86_64-pc-linux/./gcc/
-L/var/tmp/build/gcc-svn/build-x86_64-pc-linux/x86_64-pc-mingw32/winsup/mingw
-L/var/tmp/build/gcc-svn/build-x86_64-pc-linux/x86_64-pc-mingw32/winsup/w32api/lib
-isystem /var/tmp/build/gcc-svn/gcc/winsup/mingw/include -isystem
/var/tmp/build/gcc-svn/gcc/winsup/w32api/include
-B/var/tmp/rt/x86_64-pc-mingw32/bin/
-B/var/tmp/rt/x86_64-pc-mingw32/lib/ -isystem
/var/tmp/rt/x86_64-pc-mingw32/include -isystem
/var/tmp/rt/x86_64-pc-mingw32/sys-include -O2 -g -g -O2 -O2
-I../../gcc/gcc/../winsup/w32api/include -O2 -g -g -O2 -DIN_GCC
-DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../.././gcc -I../../../gcc/libgcc
-I../../../gcc/libgcc/. -I../../../gcc/libgcc/../gcc
-I../../../gcc/libgcc/../include -DHAVE_CC_TLS -o _muldi3.o -MT
_muldi3.o -MD -MP -MF _muldi3.dep -DL_muldi3 -c
../../../gcc/libgcc/../gcc/libgcc2.c \
prev parent reply other threads:[~2007-12-22 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 20:39 NightStrike
2007-12-20 21:23 ` Kaz Kylheku
2007-12-21 9:17 ` NightStrike
2007-12-21 18:30 ` Kaz Kylheku
2007-12-22 17:22 ` NightStrike
2007-12-22 17:46 ` Brian Dessent
2007-12-22 17:54 ` NightStrike [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=b609cb3b0712220954i1a5df03fs6d84903bd9b8124f@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).