From: Marco Trudel <mtrudel@gmx.ch>
To: gnustuff@thisiscool.com
Cc: tromey@redhat.com, GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: FYI: 2 patches for RH 4.1 branch
Date: Sat, 17 Feb 2007 08:31:00 -0000 [thread overview]
Message-ID: <45D6BD39.4070303@gmx.ch> (raw)
In-Reply-To: <091XXSUOE0RKGXVLK2ZOKMG94LFC941.45d66014@parallels>
Mohan Embar wrote:
> Hi Tom,
>
> I'm still stuck on this error when trying to build
> the cross compiler:
>
> ==================================================
> gcc -c -O2 -g0 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I/datal/gcc/gcc/gcc
> -I/datal/gcc/gcc/gcc/. -I/datal/gcc/gcc/gcc/../include -I/datal/gcc/gcc/gcc/../libcpp/include -I/datal/gcc/gmp_mpfr/include -I/datal/gcc/gmp_mpfr/include -I/datal/gcc/gcc/gcc/../libdecnumber -I../libdecnumber -DSTANDARD_STARTFILE_PREFIX=\"../../../\" -DSTANDARD_EXEC_PREFIX=
> \"/datal/gcc/build/crossgcc/lib/gcc/\" -DSTANDARD_LIBEXEC_PREFIX=\"/datal/gcc/build/crossgcc/libexec/gcc/\" -DDEFAULT_TARGET_VERSION=\"4.3.0\" -DDEFAULT_TARGET_MACHINE=\"i686-pc-mingw32\" -DSTANDARD_BINDIR_PREFIX=\"/datal/gcc/build/crossgcc/bin/\" -DTOOLDIR_BASE_PREFIX=\"../../../../\" -
> DTARGET_SYSTEM_ROOT=\"/datal/gcc/build/crossgcc/sys-root\" -DTARGET_SYSTEM_ROOT_RELOCATABLE `test "X${SHLIB_LINK}" = "X" || test "no" != "yes" || echo "-DENABLE_SHARED_LIBGCC"` `test "X${SHLIB_MULTILIB}" = "X" || echo "-DNO_SHARED_LIBGCC_MULTILIB"` \
> -I. -I. -I/datal/gcc/gcc/gcc -I/datal/gcc/gcc/gcc/. -I/datal/gcc/gcc/gcc/../include -I/datal/gcc/gcc/gcc/../libcpp/include -I/datal/gcc/gmp_mpfr/include -I/datal/gcc/gmp_mpfr/include -I/datal/gcc/gcc/gcc/../libdecnumber -I../libdecnumber /datal/gcc/gcc/gcc/cp/g++spec.c)
> /datal/gcc/build/crossgcc/i686-pc-mingw32/bin/as: unrecognized option `-Qy'
> make[2]: *** [g++spec.o] Error 1
> ==================================================
>
> For some reason, it's trying to use the cross assembler with
> the build compiler :( I haven't really had time to troubleshoot
> this, which is why I haven't been responsive with these two
> patches.
I'm looking for the second. So you can concentrate on the ProcessBuilder
one.
> /datal/gcc/build/crossgcc/i686-pc-mingw32/bin/ isn't
> in my path, so I don't know why it wants to use this as.
>
> The last time I tried doing this was a day or two ago. Marco:
> when was the last time you got and built the trunk?
rev 121'693. But I will do an update today. I'll inform you if it works...
Marco
> If this trunk is busted anyway and it's not just my configuration,
> I don't see the harm in checking this in. That way I don't have
> to regenerate the world and do a full build of the native compiler
> just to build my cross compiler.
>
> -- Mohan
> http://www.thisiscool.com/
> http://www.animalsong.org/
>
>
>
next prev parent reply other threads:[~2007-02-17 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 21:11 Tom Tromey
2007-02-17 1:53 ` Mohan Embar
2007-02-17 8:31 ` Marco Trudel [this message]
2007-02-17 21:35 ` Marco Trudel
2007-02-17 23:08 ` Mohan Embar
2007-02-18 10:54 ` Marco Trudel
2007-02-19 13:10 ` Mohan Embar
2007-02-19 13:21 ` Marco Trudel
2007-02-21 12:46 ` jdwp build failure Marco Trudel
2007-02-21 18:05 ` Mohan Embar
2007-02-22 2:04 ` Tom Tromey
2007-02-22 2:37 ` Mohan Embar
2007-02-22 8:10 ` Marco Trudel
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=45D6BD39.4070303@gmx.ch \
--to=mtrudel@gmx.ch \
--cc=gnustuff@thisiscool.com \
--cc=java-patches@gcc.gnu.org \
--cc=tromey@redhat.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).