From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot rebuild autobuild
Date: Mon, 13 Nov 2017 11:27:58 +0100 [thread overview]
Message-ID: <20171113102757.ir7so5o7h7zopcvq@dell5510> (raw)
Hi Peter,
I'm trying to fix failing feh on mips64el [1] (btw an easy fix, just to add -std=c99 or
-std=c11 to TARGET_CFLAGS either globally or just for this toolchain/architecture).
But I cannot rebuild it as it fails to pass configure:
$ make distclean
$ wget -c http://autobuild.buildroot.net/results/bf31199cdaa18971a9b599c26fbefac73b2d6f30/config -O .config.old
$ make olddefconfig
$ make
make: *** No rule to make target 'toolchain-external-custom', needed by '/home/foo/install/src/buildroot.git/output/build/toolchain-external/.stamp_configured'. Stop.
What can be wrong? I've done it this way in the past (with other autobuild items, which
had different toolchains).
Kind regards,
Petr
[1] http://autobuild.buildroot.net/results/bf31199cdaa18971a9b599c26fbefac73b2d6f30
next reply other threads:[~2017-11-13 10:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 10:27 Petr Vorel [this message]
2017-11-13 11:06 ` [Buildroot] Cannot rebuild autobuild Baruch Siach
2017-11-13 14:42 ` Petr Vorel
2017-11-14 22:44 ` Peter Seiderer
2017-11-15 12:58 ` Petr Vorel
2017-11-15 23:03 ` Arnout Vandecappelle
2017-11-15 23:19 ` Peter Seiderer
2017-11-15 23:40 ` Arnout Vandecappelle
2017-11-16 7:29 ` Petr Vorel
2017-11-16 13:43 ` Arnout Vandecappelle
2017-11-18 21:22 ` Peter Seiderer
2017-11-20 21:44 ` Yann E. MORIN
2017-11-18 21:32 ` Peter Seiderer
2017-11-21 20:16 ` Petr Vorel
2017-11-25 15:01 ` Yann E. MORIN
2017-11-25 16:34 ` Arnout Vandecappelle
2017-11-29 21:19 ` Petr Vorel
2017-12-15 20:22 ` Petr Vorel
2017-12-15 20:23 ` [Buildroot] FW: " Kees van Unen
2017-11-16 7:14 ` [Buildroot] " Petr Vorel
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=20171113102757.ir7so5o7h7zopcvq@dell5510 \
--to=petr.vorel@gmail.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