Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Moore <will.moore@beraninstruments.com>
To: buildroot@busybox.net
Subject: [Buildroot] bug when doing clean kernel build?
Date: Wed, 19 Jan 2011 10:07:46 -0000	[thread overview]
Message-ID: <F25ADE2AF76246FD958773C4133D8E24@beraninstruments.com.local> (raw)
In-Reply-To: <AANLkTikJiXF-w3baF2POeVr5Zh_sGUkdS+UQCQFmzb4g@mail.gmail.com>

Hi Kyle,

> -----Original Message-----
> From: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net]
> On Behalf Of Kyle Hayes
> Sent: 17 January 2011 21:01
> 
> I'm not sure if this is a code bug or a user bug :-)
> 
> I'm trying to repeat my problems with openssh segfaulting and to do
> that I'm trying to build with make xconfig; make clean; make.
> However, when I do this, I see that the Linux kernel, 2.6.37, is made
> with Pentium Pro selected and I explicitly selected i486 in the
> Buildroot config.  I can go in after the make finishes and reconfigure
> the kernel again to get the right processor type.  Is this expected
> behavior?

FWIW I believe configuring buildroot with i486 processor builds you a
toolchain for an i486.  A i486 toolchain seems to work well for me on a
vortex86dx.

I tend to configure buildroot to pick up a kernel config:

 make menuconfig

Select "Kernel" then "Linux Kernel".
Select "Kernel configuration (Using a defconfig)" and select "Using a custom
config file".
Select "() Configuration file path" and enter the path to your desired
kernel config.

Others with a better understanding can tell you if what you are experiencing
might be considered a bug...

X-Linux provided kernel configs changed (quite considerably) between v5.6
and v5.7 as to quite what processor / processor features they declare the
vortex86dx to have, the same may be true for the vortex86mx.  Perhaps you
can gain some understanding from a diff of these?

Regards,

Will

> 
> Best,
> Kyle
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2011-01-19 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 21:01 [Buildroot] bug when doing clean kernel build? Kyle Hayes
2011-01-19 10:07 ` Will Moore [this message]
2011-01-24 16:33 ` 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=F25ADE2AF76246FD958773C4133D8E24@beraninstruments.com.local \
    --to=will.moore@beraninstruments.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