From: GeunSik Lim <leemgs1@gmail.com>
To: John Kacur <jkacur@redhat.com>
Cc: williams <williams@redhat.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
tglx <tglx@linutronix.de>
Subject: Re: [PATCH]cyclictest: CFLAGS to support static compiliation with ARM Crosscompiler
Date: Thu, 21 Jan 2010 22:10:46 +0900 [thread overview]
Message-ID: <49b7c2351001210510r545a086er2fe6badcd3657fa6@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1001211201340.3873@localhost.localdomain>
On Thu, Jan 21, 2010 at 8:40 PM, John Kacur <jkacur@redhat.com> wrote:
>
>
> On Thu, 21 Jan 2010, GeunSik Lim wrote:
>
>> On Thu, Jan 21, 2010 at 9:40 AM, John Kacur <jkacur@redhat.com> wrote:
>> >
>> > Did you leave something out?
>> Not at all.
>> I summary, We have to change CFLAGS from "-lpthread -lrt" to "-lrt
>> -lpthread" to compile
>> rt-tests source successfully for static linking with GCC based arm
>> cross compiler.
>>
>> This is testcase.
>> Fedora11#> git clone
>> git://git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rt-tests.git
>> Fedora11#> cd rt-tests
>> Fedora11#> vi Makefile ( for static linking)
>> CFLAGS += -O2 -static <--- Edit this line.
>> Fedora11#> make CC=arm-linux-eabi-gcc
>> We will meet some errors like "undefined reference to . . . . . .
>> " messages.
>
> Okay, I tested that change on normal x86_64 with the static flag, and it
> does seem to work, so I have no problem with your change.
Thank you for verification on X86 64bit.
For reference, I tested that change on X86 32bit with the "-static"option.
>
> Are you sure you need a -static link flag for embedded? I was talking to
> another arm developer who also cross compiles but doesn't need it.
Of course. In general, Most embedded developers use shared linking for
Embedded environment. But, Consider some case like Speedup and
independent binary for debugging. In this case, We need useful
"-static"option.
>
> Also, the reason I asked whether something was missing, is that the text
> to your patch contains "Subject: [PATCH 2/2] bugfix: Support static
> linking(-static) with"
>
> so I was wondering where Patch 1/2 was.
>
Sorry. I mistook.:)
Patch is just one.
> Thanks.
>
--
Regards,
GeunSik Lim ( Samsung Electronics )
Blog : http://blog.naver.com/invain/
e-Mail: geunsik.lim@samsung.com
leemgs@gmail.com , leemgs1@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-01-21 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 4:04 [PATCH]cyclictest: Arrange alphabetically for readability of "cyclictest --help" GeunSik Lim
2010-01-21 0:09 ` [PATCH]cyclictest: CFLAGS to support static compiliation with ARM Crosscompiler GeunSik Lim
2010-01-21 0:40 ` John Kacur
2010-01-21 1:37 ` GeunSik Lim
2010-01-21 11:40 ` John Kacur
2010-01-21 13:10 ` GeunSik Lim [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=49b7c2351001210510r545a086er2fe6badcd3657fa6@mail.gmail.com \
--to=leemgs1@gmail.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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).