Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot-2.18.11 fails?
Date: Sun, 10 Feb 2019 08:14:43 +0100	[thread overview]
Message-ID: <20190210081443.348c14be@gmx.net> (raw)
In-Reply-To: <e40ef8db-c9df-c6db-7e61-aac0f190712a@lamiaworks.com.au>

Hello scsijon,

On Sun, 10 Feb 2019 15:20:45 +1100, scsijon <scsijon@lamiaworks.com.au> wrote:

> I thought i'd try it after so many years.
> I thought i'd try the last complete version before trying a snapshot.
> 
> So, what I did was to download and unpacked the 2018.11 package from 
> your site.

2018.11.2, 2018.11.1 or 2018.11?

> 
> Went into make menuconfig and changed (to match what I am use to working 
> with)>  
> target Architecture to x86_64;
> toolchain to glibc;
> gcc version to 8.x;
> linux kernel to 4.18 and added a defcon name;
> exited.
> 
> make source (to download the packages required so I could build offline);
> 
> make.
> 
> All went well until host-gcc-final-8.2.0 where it errored, failed and 
> exited.

Should not happen ;-), mind to share your .config/defconfig file?

Regards,
Peter

> 
> Before I consider proceeding further, could I have some help and advice 
> with this please. I would have thought this should have been ok.
> 
> I have attached the relevant section of the log file.
> 
> thanks
> scsijon
> 
> 

  reply	other threads:[~2019-02-10  7:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-10  4:20 [Buildroot] Buildroot-2.18.11 fails? scsijon
2019-02-10  7:14 ` Peter Seiderer [this message]
     [not found] <e5695acd-7280-74a5-dd40-429e4baf7fc3@lamiaworks.com.au>
     [not found] ` <0fbddf2c-9da7-80a9-a890-ec1001ac6d3f@lamiaworks.com.au>
2019-02-12 19:19   ` Peter Seiderer
2019-02-12 22:07     ` scsijon
2019-02-13 18:56       ` Peter Seiderer
2019-02-14  2:27         ` scsijon
2019-02-15 20:49           ` Peter Seiderer
2019-02-16  2:09             ` scsijon

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=20190210081443.348c14be@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