All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe <zentrale.at.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot toolchain fails to build kernel: "ld: no machine record defined"
Date: Mon, 21 Jan 2008 18:27:52 +0100	[thread overview]
Message-ID: <4794D618.4000005@gmail.com> (raw)
In-Reply-To: <20080121164720.GA22900@aon.at>

In the meantime i managed to find the old kernel config in our backups, 
and this kernel builds fine. So i'm guilty messing it up - shame on me! :-(

Nevertheless thanks a lot,
Greetz Joe

Bernhard Fischer schrieb:
> On Mon, Jan 21, 2008 at 05:20:43PM +0100, Joe wrote:
>> Hi all!
>>
>> Today I tried to build a new kernel for my dev-board. Last time i did 
>> this was Nov 2007, when i also used a buildroot-created toolchain which 
>> worked absolutely fine. Today it compiles a lot, and then backs out with
>>
>> "arm-linux-ld: no machine record defined" in the file .tmp_vmlinux1
>>
>> After googling a lot, i found some messages including one by Russell 
>> King indicating that there is probably something wrong with the used 
>> binutils and that it should be reported to the binutils people. But 
>> because i used the buildroot chain, i thought i'd ask here first.
>> Tried combinations include gcc 4.2.1 and 4.1.2 as well as binutils 2.18 
>> and 2.17 on kernels 2.6.22.10 and 2.6.23.14. Every possible combination 
>> was given a try with the same results.
>>
>> Are there any ideas on this?
> 
> Please send me your buildroot.config and (if it's not the default) your
> uClibc.config and kernel.config for me to reproduce.
> 


-- 
Sepp "ZaP" Holzmayr

please reply to:
zentrale.at.work at gmail.com

watch out for:
www.rocksociety.de

      parent reply	other threads:[~2008-01-21 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 16:20 [Buildroot] buildroot toolchain fails to build kernel: "ld: no machine record defined" Joe
     [not found] ` <20080121164720.GA22900@aon.at>
2008-01-21 16:56   ` Joe
2008-01-21 17:27   ` Joe [this message]

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=4794D618.4000005@gmail.com \
    --to=zentrale.at.work@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.