From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help to fix Microblaze issues in Buildroot
Date: Wed, 20 Nov 2013 15:09:20 +0100 [thread overview]
Message-ID: <20131120150920.4eaf92a4@skate> (raw)
In-Reply-To: <CAM+bi4sL0io7iuRA7AE_CNhs5sTTqc2oRS7As2pCEqkFwcr2Sg@mail.gmail.com>
Dear Alvaro Gamez,
On Wed, 20 Nov 2013 14:56:17 +0100, Alvaro Gamez wrote:
> The bad news is that Spenser's patches require some work. Most of it
> is easy and I've already done it myself, I can resubmit these patches
> with the little changes I made to have it fully working.
Did you realize that Spenser patches apply on top of the patches from
Mischa Jonker?
> However, there's a detail that affects other buildroot parts.
>
> gcc.mk file requires the source code to be downloaded as a .tar.bz2
> file.
>
> However, the new github helper is only able to download .tar.gz
> files. I don't think this is due to the new github helper but to
> github itself, that only provides gziped versions of its files.
>
> gcc.mk defines HOST_GCC_EXTRACT_CMDS as:
>
> $(BZCAT) $(DL_DIR)/$(GCC_SOURCE) | \
> $(TAR) $(TAR_STRIP_COMPONENTS)=1 -C $(@D) \
> --exclude='libjava/*' \
> --exclude='libgo/*' \
> --exclude='gcc/testsuite/*' \
> --exclude='libstdc++-v3/testsuite/*' \
> $(TAR_OPTIONS) -
> mkdir -p $(@D)/libstdc++-v3/testsuite/
> echo "all:" > $(@D)/libstdc++-v3/testsuite/Makefile.in
> echo "install:" >> $(@D)/libstdc++-v3/testsuite/Makefile.in
>
> So... now I have the question:
>
> Is it necessary to manually invoke bzcat? Why don't we let tar deal
> with the matter of deciding which uncompresser to use, since it now
> by defaults can detect it without the need to pass any 'z' or 'j'
> parameter?
For example, this specific problem is solved by Mischa Jonker
patches. See http://patchwork.ozlabs.org/patch/290981/.
See also the cover letter from Spenser at
http://lists.busybox.net/pipermail/buildroot/2013-November/082590.html,
which explains what are the dependencies of his patch series.
Which other problems have you seen?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-20 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 16:54 [Buildroot] Help to fix Microblaze issues in Buildroot Thomas Petazzoni
[not found] ` <CAM+bi4vGmKHRA3j0ua-dsOBzTuj-BPrM2+z3papeyfDjjazhgw@mail.gmail.com>
2013-11-20 10:03 ` Alvaro Gamez
2013-11-20 10:10 ` Thomas Petazzoni
2013-11-20 10:28 ` Thomas De Schampheleire
2013-11-20 10:32 ` Alvaro Gamez
2013-11-20 10:36 ` Alvaro Gamez
2013-11-20 10:41 ` Thomas Petazzoni
2013-11-20 12:40 ` Spenser Gilliland
2013-11-20 13:56 ` Alvaro Gamez
2013-11-20 14:00 ` Spenser Gilliland
2013-11-20 14:09 ` Thomas Petazzoni [this message]
2013-11-20 14:15 ` Alvaro Gamez
2013-11-20 14:18 ` Thomas Petazzoni
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=20131120150920.4eaf92a4@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.