From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH] fix GCC 4.3.3 sources in stable/2009 branch
Date: Tue, 07 Apr 2009 19:16:33 +0200 [thread overview]
Message-ID: <grg1ph$14n$1@ger.gmane.org> (raw)
In-Reply-To: <49DB854A.4070908@cs.cmu.edu>
On 07-04-09 18:54, David Huggins-Daines wrote:
> Tom Rini wrote:
>>
>> First, this is fixed in .dev now, by fixing all of the gcc recipes
>> (except for csl ones) to use ${GNU_MIRROR} and updating the checksums
>> file. Second, ftp.gnu.org/gnu is correct as 'pub' is just a symlink to
>> '.'.
> Yeah, actually, after trying to rebuild, I agree. Changing bitbake.conf
> is a very bad idea.
>
> However I still think the changes to the gcc recipes and checksums.ini
> should be merged into the stable branch, otherwise it is not possible to
> build any recent versions of GCC (and in particular, thumb support seems
> not to work properly without using 4.3.3)
Anyone is free to send a patch to this mailinglist to add to stable.
It's really easy:
Powerbook-3:openembedded koen$ cat contrib/mail-diff.sh
#!/bin/sh
# This script will fetch an 'mbox' patch from patchwork and git am it
# usage: mail-diff.sh <rev>
# example: 'pw-am.sh 3a485444f0dd07fd2315769db3f6f46e3972134e'
PATCHNAME="$(git format-patch -s -1 $1)"
sed -i -e 's:\[PATCH:\[STABLE\]\[PATCH:g' $PATCHNAME
git send-email --from "Koen Kooi <k.kooi@student.utwente.nl>" --to
openembedded-devel@lists.openembedded.org $PATCHNAME
rm $PATCHNAME
regards,
Koen
prev parent reply other threads:[~2009-04-07 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 15:16 [PATCH] fix GCC 4.3.3 sources in stable/2009 branch David Huggins-Daines
2009-04-07 16:44 ` Tom Rini
2009-04-07 16:54 ` David Huggins-Daines
2009-04-07 17:02 ` Tom Rini
2009-04-07 17:16 ` Koen Kooi [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='grg1ph$14n$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.