From: stefan_seefeld@mentor.com (Stefan Seefeld)
Subject: [lttng-dev] arm gcc compile lttng-tool fail
Date: Thu, 27 Mar 2014 09:20:15 -0400 [thread overview]
Message-ID: <5334258F.80706@mentor.com> (raw)
In-Reply-To: <CANudz+soZbO-GGZyXrNZdEQRp3Nz6xUO_p-mnTEeRiGA4MJLew@mail.gmail.com>
On 2014-03-27 09:09, loody wrote:
> hi Stefan:
>
>
>>
>> Exactly. Compiling src/common/consumer.c,
>> src/common/kernel-consumer/kernel-consumer.c, and
>> src/common/ust-consumer/ust-consumer.c with -O1 instead of -O2 worked
>> for us. And if you are afraid to mess with the build system, you can
>> also inject
>>
>> #pragma GCC optimize ("O1")
>>
>> on top of those files to override the command-line optimization option.
>>
> I use CFLAGS="-O1" while executing configure
> But I get below message
> CCLD lttng-consumerd
> /media/sdb2/toolchain/arm/arm-v7a8v4r3-20131011/bin/../lib/gcc/arm-v7a8v4r3-linux-gnueabi/4.7.4/../../../../arm-v7a8v4r3-linux-gnueabi/bin/ld:
> health_state: TLS reference in
> ../../../src/common/.libs/libconsumer.a(consumer.o) mismatches non-TLS
> reference in ../../../src/common/.libs/libconsumer.a(consumer-timer.o)
> ../../../src/common/.libs/libconsumer.a: could not read symbols: Bad value
> collect2: error: ld returned 1 exit status
> make[3]: *** [lttng-consumerd] Error 1
>
> is that related to optimization?
I haven't seen that error before. Did you run 'make clean' before ?
Perhaps your link command is now picking up object files compiled before
and after your reconfiguration, and there are other changes introduced
that are incompatible. The optimization flag alone shouldn't cause any
incompatibility.
Stefan
--
Stefan Seefeld
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software/
prev parent reply other threads:[~2014-03-27 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 12:26 loody
2014-03-27 12:41 ` Stefan Seefeld
2014-03-27 12:53 ` loody
2014-03-27 12:58 ` Stefan Seefeld
2014-03-27 13:09 ` loody
2014-03-27 13:20 ` Stefan Seefeld [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=5334258F.80706@mentor.com \
--to=stefan_seefeld@mentor.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