linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Lorenzo Colitti <lorenzo@google.com>
Cc: Thomas Meyer <thomas@m3y3r.de>,
	"user-mode-linux-devel@lists.sourceforge.net"
	<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH v4] um: Switch clocksource to hrtimers
Date: Wed, 18 Nov 2015 14:40:38 +0100	[thread overview]
Message-ID: <564C7FD6.40909@nod.at> (raw)
In-Reply-To: <CAKD1Yr2psSBLn3hDnsci=4S4Mey0UojUE5d_qEd9sdbhn+8EEg@mail.gmail.com>

Hi!

Am 18.11.2015 um 14:32 schrieb Lorenzo Colitti:
> On Wed, Nov 18, 2015 at 5:06 PM, Richard Weinberger <richard@nod.at> wrote:
>>
>>> That command line doesn't work, but if you remove the -lrt and put it
>>> at the end of the line, it starts working. Is the order significant?
>>> Or is it a bug in GCC's command line parsing?
>>
>> The order matters.
>> -lrt has to be placed after all object files which need the rt library.
>> Can you double check whether this is the case?
> 
> No, it's not the case. The error is when linking arch/um/os-Linux/built-in.o:
> 
> arch/um/os-Linux/built-in.o: In function `os_timer_create':
> /android/kernel/android/arch/um/os-Linux/time.c:51: undefined
> reference to `timer_create'
> 
> and in the generated command line, -lrt appears
> beforearch/um/os-Linux/built-in.o:
> 
> + gcc -Wl,-rpath,/lib64 -m64 -Wl,-rpath,/lib -Wl,--wrap,malloc
> -Wl,--wrap,free -Wl,--wrap,calloc -Wl,-m -Wl,elf_x86_64 -lrt -o
> .tmp_vmlinux1 -Wl,-T,./arch/um/kernel/vmlinux.lds init/built-in.o
> -Wl,--start-group usr/built-in.o arch/um/kernel/built-in.o
> arch/um/drivers/built-in.o arch/um/os-Linux/built-in.o
> arch/x86/crypto/built-in.o arch/x86/um/built-in.o kernel/built-in.o
> certs/built-in.o mm/built-in.o fs/built-in.o ipc/built-in.o
> security/built-in.o crypto/built-in.o block/built-in.o lib/lib.a
> lib/built-in.o drivers/built-in.o sound/built-in.o firmware/built-in.o
> net/built-in.o virt/built-in.o -Wl,--end-group -lutil
> 
> Taking -lrt out of arch/um/Makefile and putting it into
> link-vmlinux.sh, as per the patch I suggested above, results in -lrt
> being the last thing on the command line, after -lutil.
> 

Okay, please send a proper patch. :-)

Thanks,
//richard

------------------------------------------------------------------------------
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel


      reply	other threads:[~2015-11-18 13:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 16:16 [uml-devel] [PATCH v4] um: Switch clocksource to hrtimers Anton Ivanov
2015-11-02 21:50 ` Richard Weinberger
2015-11-02 22:13   ` Anton Ivanov
2015-11-03  7:11     ` Anton Ivanov
2015-11-03  7:58       ` Thomas Meyer
2015-11-06 21:56 ` Richard Weinberger
2015-11-07 10:29   ` Anton Ivanov
2015-11-07 10:32     ` Richard Weinberger
2015-11-18  1:20   ` Lorenzo Colitti
2015-11-18  7:00     ` Anton Ivanov
2015-11-18  7:10       ` Lorenzo Colitti
2015-11-18  8:06         ` Richard Weinberger
2015-11-18 13:32           ` Lorenzo Colitti
2015-11-18 13:40             ` Richard Weinberger [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=564C7FD6.40909@nod.at \
    --to=richard@nod.at \
    --cc=lorenzo@google.com \
    --cc=thomas@m3y3r.de \
    --cc=user-mode-linux-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).