From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: [RFC]: Toolchain build sequence alteration.
Date: Wed, 16 Jul 2008 08:27:41 -0700 [thread overview]
Message-ID: <487E136D.5040308@gmail.com> (raw)
In-Reply-To: <g5kch2$egl$1@ger.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> --- conf/distro/angstrom-2008.1.conf
> f64ebcf55e85b504d3be169befac3c7981aa74d9
> +++ conf/distro/angstrom-2008.1.conf
> 8703f595671685f632e51c96d1be75cdceddfe83
> @@ -70,9 +70,8 @@ PREFERRED_VERSION_linux-libc-headers =
> PREFERRED_VERSION_linux-libc-headers = "2.6.23"
>
> #Prefer glibc 2.6 and uclibc 0.9.29, these have had the most testing.
> -PREFERRED_VERSION_glibc ?= "2.6.1"
> -PREFERRED_VERSION_glibc-intermediate ?= "2.6.1"
> -PREFERRED_VERSION_glibc-initial ?= "2.6.1"
> +PREFERRED_VERSION_glibc ?= "2.3.6"
> +PREFERRED_VERSION_glibc-initial ?= "2.3.6"
>
> #Everybody else can just use this:
> -ANGSTROM_GCC_VERSION ?= "4.2.4"
> +ANGSTROM_GCC_VERSION ?= "3.4.4"
>
> @@ -123,6 +122,7 @@ PREFERRED_PROVIDER_virtual/${TARGET_PREF
> # Virtuals:
> PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}binutils = "binutils-cross"
> PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}gcc-initial =
> "gcc-cross-initial"
> +PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}gcc-intermediate =
> "gcc-cross-intermediate"
> PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}gcc = "gcc-cross"
> PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}g++ = "gcc-cross"
>
>
> You probably only want the PREFERRED_PROVIDER bit, not changing angstrom
> back to the dark ages :)
yes thats true. I have been testing different compiler versions so this change remained in the patch. It wont be committed.
>
> You also change handling of ctr*.o, but that was intended, right?
Thats intended. They are needed to build GCC with shared lib support
>
> I see no obvious errors besides the above, but as I said, I haven't
> tested it.
Thanks for your review.
>
> regards,
>
> Koen
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIfhNtHnJKy6V6em4RAuNMAJ4ubEC77wxEbrHlLI/g4kZ0Ud6ECgCgjqbw
ZF0uKt8rhh/Sq4Qb6hCmP0U=
=dsS6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-07-16 15:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 1:58 [RFC]: Toolchain build sequence alteration Khem Raj
2008-07-15 7:34 ` Henning Heinold
2008-07-16 8:10 ` Khem Raj
2008-07-16 8:46 ` Koen Kooi
2008-07-16 15:27 ` Khem Raj [this message]
2008-07-16 20:43 ` Leon Woestenberg
2008-07-17 8:43 ` Khem Raj
2008-07-22 0:28 ` Khem Raj
[not found] ` <20080720014112.GA13759@oberlord>
2008-07-23 9:04 ` Khem Raj
2008-07-24 9:10 ` Richard Purdie
2008-07-24 16:05 ` Richard Purdie
2008-07-24 16:18 ` Koen Kooi
2008-07-25 7:33 ` Khem Raj
2008-07-25 10:01 ` Henning Heinold
2008-07-25 16:06 ` Khem Raj
2008-07-28 6:27 ` SH7760 Problems Stefano Regno
2008-08-02 12:03 ` [RFC]: Toolchain build sequence alteration Koen Kooi
2008-08-02 15:14 ` Phil Blundell
2008-08-02 15:45 ` Koen Kooi
2008-08-03 2:47 ` Khem Raj
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=487E136D.5040308@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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