Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot rebuild autobuild
Date: Tue, 14 Nov 2017 23:44:09 +0100	[thread overview]
Message-ID: <20171114234409.114f002f@gmx.net> (raw)
In-Reply-To: <20171113144231.gddccsqlelrhrokw@dell5510>

Hello Petr,

On Mon, 13 Nov 2017 15:42:32 +0100, Petr Vorel <petr.vorel@gmail.com> wrote:

> > 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

Your should store the downloaded config file definitely as '.config' instead of '.config.old' (there is only
the way .config --> .config.old and not the other way round in buildroot)...
 
> > $ 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).  

Same here with a fresh installed openSUSE Tumbleweed x86_64 without 32-bit support packages installed.

Until commit ec54092c916440501006bfa51a820eb953100510 ('toolchain-external-custom: new package'), or with
2016.11.3 the same config gives the following error instead:

[...]
Cannot execute cross-compiler '.../host/opt/ext-toolchain/bin/x86_64-ctng_locales-linux-gnu-gcc'
make[1]: *** [package/pkg-generic.mk:209: .../build/toolchain-external/.stamp_configured] Error 1
make: *** [Makefile:16: _all] Error 2

Maybe the toolchain definition should select BR2_HOSTARCH_NEEDS_IA32_LIBS?

Regards,
Peter

> 
> > [1] http://autobuild.buildroot.net/results/bf31199cdaa18971a9b599c26fbefac73b2d6f30  
> 
> And of course, I'm working on current master.
> 
> 
> Kind regards,
> Petr
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2017-11-14 22:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 10:27 [Buildroot] Cannot rebuild autobuild Petr Vorel
2017-11-13 11:06 ` Baruch Siach
2017-11-13 14:42 ` Petr Vorel
2017-11-14 22:44   ` Peter Seiderer [this message]
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=20171114234409.114f002f@gmx.net \
    --to=ps.report@gmx.net \
    --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