From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem using Linux kernel archive from Gitorious
Date: Thu, 17 Jan 2013 17:35:43 +0200 [thread overview]
Message-ID: <50F81A4F.6000705@petroprogram.com> (raw)
In-Reply-To: <20130117160133.61661524@skate>
17.1.2013 17:01, Thomas Petazzoni kirjoitti:
> The problem here is that since the filename doesn't end with .tar.gz,
> Buildroot doesn't know which extraction method to apply, and therefore
> doesn't apply any, which leads Buildroot to try to execute your tarball.
>
> Hum, I am not sure how to handle that. Should we try to extract simply
> with tar something that does not have an extension?
if you use tar with -a switch it is smart enough to extract it
correctly. Even if wrong extension or no extension at all.
For example:
mv bison-2.5.tar.gz bison-2.5.tar.xyz
tar -xaSvf bison-2.5.tar.xyz
mv bison-2.5.tar.gz bison-2.5
tar -xaSvf bison-2.5
Regards
Stefan
next prev parent reply other threads:[~2013-01-17 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 14:47 [Buildroot] Problem using Linux kernel archive from Gitorious Aras Vaichas
2013-01-17 15:01 ` Thomas Petazzoni
2013-01-17 15:17 ` Stephan Hoffmann
2013-01-17 15:35 ` Stefan Fröberg [this message]
2013-01-19 13:20 ` Arnout Vandecappelle
2013-01-21 11:30 ` Aras Vaichas
2013-01-24 6:32 ` Arnout Vandecappelle
2013-01-24 13:10 ` Peter Korsgaard
2013-01-25 11:53 ` Aras Vaichas
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=50F81A4F.6000705@petroprogram.com \
--to=stefan.froberg@petroprogram.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.