From: Adam Megacz <megacz@cs.berkeley.edu>
To: java-patches@gcc.gnu.org
Subject: canadian vs build==host configury
Date: Thu, 21 Dec 2006 19:12:00 -0000 [thread overview]
Message-ID: <x3hcvpkqrz.fsf_-_@nowhere.com> (raw)
In-Reply-To: <LIYSDAGDHENI64OJKGJELG63FDJ4XGA.458ad753@parallels>
Mohan Embar <gnustuff@thisiscool.com> writes:
> I don't see how this:
>
>> > + GCJ="$built_gcc_dir/gcj -B$built_gcc_dir/"
>
> ...could possibly be right. Adam, are you building on Linux or Mactel?
Linux.
> What the above line is assuming is that the intermediate compiler is
> suitable for building libgcj. This is only true when build=host, which
That is the case; at the moment I am doing (build==host)!=target.
The previous configury was broken for that case.
> That means building the cross compiler, installing it, then adjusting your
> system path accordingly before doing the crossed-native build.
Perhaps, but this should not be necessary when build==host.
If I understand your email correctly, you need to do a "make install"
before building libgcj when creating a Canadian cross-compiler and
then let libgcj's build process find the installed compiler. However,
this had not previously been required for build==host cross-compilers.
Did that change?
I think Canadian cross-builds need their own case arm in that block of
configure.ac (the "we cannot execute the compiler we just built" case,
which is not identical to the "we are making a cross-compiler" case).
- a
--
PGP/GPG: 5C9F F366 C9CF 2145 E770 B1B8 EFB1 462D A146 C380
next prev parent reply other threads:[~2006-12-21 19:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 6:07 [gcj-eclipse-merge-branch] fix cross-build configury/makery Adam Megacz
2006-12-05 10:21 ` Andrew Haley
2006-12-21 2:43 ` Adam Megacz
2006-12-21 5:28 ` Mohan Embar
2006-12-21 6:42 ` Adam Megacz
2006-12-21 8:41 ` Adam Megacz
2006-12-21 17:40 ` retracting my retraction [patch included] Adam Megacz
2006-12-21 17:50 ` Andrew Haley
2006-12-21 18:50 ` Mohan Embar
2006-12-21 18:52 ` Andrew Haley
2006-12-21 19:12 ` Adam Megacz [this message]
2006-12-21 20:31 ` canadian vs build==host configury (and $with_cross_host) Adam Megacz
2007-01-20 0:56 ` Tom Tromey
2007-01-20 6:46 ` Mohan Embar
2007-01-23 0:21 ` Tom Tromey
2006-12-21 21:03 ` canadian vs build==host configury Mohan Embar
2006-12-21 21:45 ` Adam Megacz
2006-12-21 22:17 ` Mohan Embar
2006-12-21 23:36 ` Adam Megacz
2006-12-22 0:04 ` Mohan Embar
2007-01-20 0:50 ` retracting my retraction [patch included] Tom Tromey
2007-01-20 6:09 ` Mohan Embar
2007-01-20 6:58 ` libjava configury logic for cross builds (was Re: retracting my retraction [patch included]) Mohan Embar
2007-01-20 10:03 ` retracting my retraction [patch included] Andrew Haley
2007-01-20 12:32 ` Marco Trudel
2007-01-20 13:18 ` Mohan Embar
2007-01-23 0:20 ` Tom Tromey
2007-02-04 3:37 ` Patch: Fix GCJH for cross builds (was Re: retracting my retraction [patch included]) Mohan Embar
2007-02-05 9:48 ` Andrew Haley
2006-12-06 23:13 ` [gcj-eclipse-merge-branch] fix cross-build configury/makery Tom Tromey
2006-12-07 0:55 ` Mohan Embar
2006-12-07 3:36 ` Mohan Embar
2006-12-07 3:28 ` Tom Tromey
2006-12-07 7:55 ` Patch [ecj]: Fix cross-configury issues / compile ecj.jar for non-shared builds Mohan Embar
2006-12-07 11:14 ` Andrew Haley
2006-12-07 13:01 ` Mohan Embar
2006-12-07 13:02 ` Andrew Haley
2006-12-07 16:39 ` Mohan Embar
2006-12-07 15:10 ` Andrew Haley
2006-12-07 16:04 ` Mohan Embar
2006-12-07 16:53 ` LockSupportTest.java Mohan Embar
2006-12-07 15:44 ` Patch [ecj]: Fix cross-configury issues / compile ecj.jar for non-shared builds Mohan Embar
2006-12-08 19:44 ` Tom Tromey
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=x3hcvpkqrz.fsf_-_@nowhere.com \
--to=megacz@cs.berkeley.edu \
--cc=java-patches@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).