From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuild reproduction and generation
Date: Mon, 26 Dec 2016 10:16:59 +0100 [thread overview]
Message-ID: <20161226101659.57238bc6@free-electrons.com> (raw)
In-Reply-To: <CADZ=QZnpVmC_hKqSMFehhdO_m9pZsK0OBcfVd4hXsbvjV==A1g@mail.gmail.com>
Hello,
On Mon, 26 Dec 2016 17:07:08 +0800, Yu-Ting, Kao wrote:
> 2016-12-26 16:52:22 (997 KB/s) -
> ?/home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/output/build/.br-i386-pentium4-full-2016.11-236-ge309abf.tar.bz2.UewivN/output?
> saved [44346526/44346526]
>
> WARNING: no hash file for br-i386-pentium4-full-2016.11-236-ge309abf.tar.bz2
> >>> toolchain-external-custom Extracting
> bzcat
> /home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/buildroot/dl/br-i386-pentium4-full-2016.11-236-ge309abf.tar.bz2
> | tar --strip-components=1 -C
> /home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/output/build/toolchain-external-custom
> --exclude='usr/lib/locale/*' -xf -
> rm -rf
> /home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/output/host/opt/ext-toolchain
> mkdir -p
> /home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/output/host/opt/ext-toolchain
> mv
> /home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/output/build/toolchain-external-custom/*
> /home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/output/host/opt/ext-toolchain/
> >>> toolchain-external-custom Patching
> >>> toolchain-external-custom Configuring
> Cannot execute cross-compiler
> '/home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/output/host/opt/ext-toolchain/bin/i686-linux-gcc.br_real'
> make[1]: ***
> [/home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/output/build/toolchain-external-custom/.stamp_configured]
> Error 1
> make: *** [_all] Error 2
This one is because for some reason the pre-built toolchain doesn't
work for you. Please
run ./output/host/opt/ext-toolchain/bin/i686-linux-gcc manually to see
what is the error message.
> 7. Sometimes may show
>
> ----------------------------------------------------------------------------------------------------
>
> --2016-12-26 16:59:07--
> http://autobuild.buildroot.org/results/358/358e2f02f42e08fe362ecd46e636c0048e77c21f//gitid
> Resolving autobuild.buildroot.org (autobuild.buildroot.org)... 94.23.254.152
> Connecting to autobuild.buildroot.org
> (autobuild.buildroot.org)|94.23.254.152|:80...
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 40 [text/plain]
> Saving to:
> ?/home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f//gitid?
>
> 100%[=========================================================================>]
> 40 --.-K/s in 0s
>
> 2016-12-26 16:59:08 (1.59 MB/s) -
> ?/home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f//gitid? saved
> [40/40]
>
> fatal: destination path 'buildroot' already exists and is not an empty
> directory.
> Cannot clone Buildroot Git repository
You have already tried to build this same build id, so Buildroot has
already been cloned. The script is not prepared for that, it assumes
you build only once a given build id. If you want to build it two time,
you are supposed to
remove /home/kao23/disk_2/358e2f02f42e08fe362ecd46e636c0048e77c21f/
between the two builds.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-26 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 8:15 [Buildroot] Autobuild reproduction and generation Yu-Ting Kao
2016-12-26 8:21 ` Thomas Petazzoni
2016-12-26 9:07 ` Yu-Ting, Kao
2016-12-26 9:16 ` Thomas Petazzoni [this message]
2016-12-26 14:32 ` Yu-Ting, Kao
2016-12-26 14:39 ` Thomas Petazzoni
2016-12-27 1:57 ` Yu-Ting, Kao
2016-12-27 9:45 ` 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=20161226101659.57238bc6@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox