public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@googlemail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Jeff Dike <jdike@addtoit.com>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: kbuild breaks um - fails to find util when linking
Date: Sat, 14 Jun 2008 01:08:44 +0200	[thread overview]
Message-ID: <4852FDFC.1020403@googlemail.com> (raw)
In-Reply-To: <20080612210615.GA7558@uranus.ravnborg.org>

Sam Ravnborg wrote:

Hi Sam , Jeff ,

> On Thu, Jun 12, 2008 at 04:13:15PM -0400, Jeff Dike wrote:
>> On Thu, Jun 12, 2008 at 08:08:59PM +0200, Sam Ravnborg wrote:
>>> Following patch will result in a building ARCH=um kernel.
>>> If it works I dunno.
>> You can just try running it.  Given its behavior with this patch so
>> far, it would be an excellent sign for it to figure out that it has no
>> root filesystem and panic.
>>
>> Anyway, I can't get it to give me a UML binary.  I see this in the
>> build output (and V=3 doesn't make it any more verbose):
>>
>>
>> 	  CHK     include/linux/compile.h
>> 	  LINK linux
>>
>> 	Compilation finished at Thu Jun 12 16:11:15
>>
>> but no linux or vmlinux in my output directory.
> 
> So appearantly kbuild thinks you have a vmlinux
> so no need to relink.
> And the line "LINK linux" implies this as well.
> 
> Please double check that you do not have a vmlinux,
> and try V=2" to see where LINK picks up the vmlinux.
> 
> My build finised:
> $ ./linux
>  ./linux: /usr/lib/libc.so.1: bad ELF interpreter: No such file or directory


I didn't tested this patch but I think LINK-$(CONFIG_LD_SCRIPT_DYN) should have -rpath / -rpath-link too since 
libc.so.* is usually in /lib and not /usr/lib.

Another thing I noticed is this hunk :

+$(shell $(CC) -print-file-name=ld-linux.so.2) \

On 64bit that should not work since it is ld-linux-x86-64.so.2 and not ld-linux.so.2

> 

> So I will take an additional look tomorrow.
> 
> 	Sam


Regards ,

Gabriel

  reply	other threads:[~2008-06-13 23:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 19:03 kbuild breaks um - fails to find util when linking Sam Ravnborg
2008-06-11 15:11 ` Jeff Dike
2008-06-11 15:23 ` Jeff Dike
2008-06-11 15:48 ` Jeff Dike
2008-06-11 19:49   ` Sam Ravnborg
2008-06-12 18:08   ` Sam Ravnborg
2008-06-12 20:13     ` Jeff Dike
2008-06-12 21:06       ` Sam Ravnborg
2008-06-13 23:08         ` Gabriel C [this message]
2008-06-18 16:51           ` Jeff Dike
2008-06-18 16:59             ` Sam Ravnborg

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=4852FDFC.1020403@googlemail.com \
    --to=nix.or.die@googlemail.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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