* [Buildroot] gcc on target system issue
@ 2012-11-15 22:20 Alexander Khryukin
2012-11-16 17:10 ` Alexander Khryukin
2012-11-16 17:30 ` Thomas Petazzoni
0 siblings, 2 replies; 7+ messages in thread
From: Alexander Khryukin @ 2012-11-15 22:20 UTC (permalink / raw)
To: buildroot
Hi all.
I'm trying to build gcc on target but it fails with
./gcc -I/home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/../include
-DHAVE_CC_TLS -o _negdi2_s.o -MT _negdi2_s.o -MD -MP -MF _negdi2_s.dep
-DSHARED -DL_negdi2 -c
/home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/libgcc2.c
In file included from
/home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/config/arm/unwind-arm.c:154:0:
/home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/unwind-arm-common.inc:
At top level:
/home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/unwind-arm-common.inc:30:21:
fatal error: sys/sdt.h: No such file or directory
compilation terminated.
make[3]: *** [unwind-arm.o] Error 1
make[3]: *** Waiting for unfinished jobs....
In file included from
/home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/unwind-c.c:29:0:
./unwind.h: In function '_Unwind_decode_typeinfo_ptr':
./unwind.h:42:45: warning: unused parameter 'base' [-Wunused-parameter]
./unwind.h: In function '__gnu_unwind_24bit':
./unwind.h:68:41: warning: unused parameter 'context' [-Wunused-parameter]
./unwind.h:68:54: warning: unused parameter 'data' [-Wunused-parameter]
./unwind.h:68:64: warning: unused parameter 'compact' [-Wunused-parameter]
make[3]: Leaving directory
`/home/user/buildroot/output/build/gcc-4.7.2-target/arm-buildroot-linux-uclibcgnueabi/libgcc'
make[2]: *** [all-target-libgcc] Error 2
make[2]: Leaving directory
`/home/user/buildroot/output/build/gcc-4.7.2-target'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/user/buildroot/output/build/gcc-4.7.2-target'
make: *** [/home/user/buildroot/output/build/gcc-4.7.2-target/.compiled]
Error 2
Also sys/sdt.h provides by systemtap
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121116/38957449/attachment.html>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] gcc on target system issue
2012-11-15 22:20 [Buildroot] gcc on target system issue Alexander Khryukin
@ 2012-11-16 17:10 ` Alexander Khryukin
2012-11-16 17:30 ` Thomas Petazzoni
1 sibling, 0 replies; 7+ messages in thread
From: Alexander Khryukin @ 2012-11-16 17:10 UTC (permalink / raw)
To: buildroot
2012/11/16 Alexander Khryukin <alexander@mezon.ru>
> Hi all.
> I'm trying to build gcc on target but it fails with
>
>
> ./gcc -I/home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/../include
> -DHAVE_CC_TLS -o _negdi2_s.o -MT _negdi2_s.o -MD -MP -MF _negdi2_s.dep
> -DSHARED -DL_negdi2 -c
> /home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/libgcc2.c
> In file included from
> /home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/config/arm/unwind-arm.c:154:0:
> /home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/unwind-arm-common.inc:
> At top level:
> /home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/unwind-arm-common.inc:30:21:
> fatal error: sys/sdt.h: No such file or directory
> compilation terminated.
> make[3]: *** [unwind-arm.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> In file included from
> /home/user/buildroot/output/toolchain/gcc-4.7.2/libgcc/unwind-c.c:29:0:
> ./unwind.h: In function '_Unwind_decode_typeinfo_ptr':
> ./unwind.h:42:45: warning: unused parameter 'base' [-Wunused-parameter]
> ./unwind.h: In function '__gnu_unwind_24bit':
> ./unwind.h:68:41: warning: unused parameter 'context' [-Wunused-parameter]
> ./unwind.h:68:54: warning: unused parameter 'data' [-Wunused-parameter]
> ./unwind.h:68:64: warning: unused parameter 'compact' [-Wunused-parameter]
> make[3]: Leaving directory
> `/home/user/buildroot/output/build/gcc-4.7.2-target/arm-buildroot-linux-uclibcgnueabi/libgcc'
> make[2]: *** [all-target-libgcc] Error 2
> make[2]: Leaving directory
> `/home/user/buildroot/output/build/gcc-4.7.2-target'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory
> `/home/user/buildroot/output/build/gcc-4.7.2-target'
> make: *** [/home/user/buildroot/output/build/gcc-4.7.2-target/.compiled]
> Error 2
>
>
>
> Also sys/sdt.h provides by systemtap
>
Bump
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121116/c1c77f5b/attachment-0001.html>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] gcc on target system issue
2012-11-15 22:20 [Buildroot] gcc on target system issue Alexander Khryukin
2012-11-16 17:10 ` Alexander Khryukin
@ 2012-11-16 17:30 ` Thomas Petazzoni
2012-11-16 21:59 ` Alexander Khryukin
1 sibling, 1 reply; 7+ messages in thread
From: Thomas Petazzoni @ 2012-11-16 17:30 UTC (permalink / raw)
To: buildroot
Dear Alexander Khryukin,
On Fri, 16 Nov 2012 01:20:32 +0300, Alexander Khryukin wrote:
> I'm trying to build gcc on target but it fails with
Why are you trying to build gcc on target? What is the purpose of
getting gcc on the target when building a small embedded Linux system
with Buildroot?
Notice that as per the decisions taken during the last Buildroot
Developers Meeting, the possibility of building gcc for the target in
Buildroot should soon be deprecated. So there is not a strong interest
to fix problems reported by users.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] gcc on target system issue
2012-11-16 17:30 ` Thomas Petazzoni
@ 2012-11-16 21:59 ` Alexander Khryukin
2012-11-17 8:10 ` Peter Korsgaard
2012-11-18 13:27 ` Arnout Vandecappelle
0 siblings, 2 replies; 7+ messages in thread
From: Alexander Khryukin @ 2012-11-16 21:59 UTC (permalink / raw)
To: buildroot
2012/11/16 Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Dear Alexander Khryukin,
>
> On Fri, 16 Nov 2012 01:20:32 +0300, Alexander Khryukin wrote:
>
> > I'm trying to build gcc on target but it fails with
>
> Why are you trying to build gcc on target? What is the purpose of
> getting gcc on the target when building a small embedded Linux system
> with Buildroot?
>
> Notice that as per the decisions taken during the last Buildroot
> Developers Meeting, the possibility of building gcc for the target in
> Buildroot should soon be deprecated. So there is not a strong interest
> to fix problems reported by users.
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>
Ah, it bad solution to deprecate gcc on target.
i'm embedded linux developer and trying to build OpenMandriva linux
for cortex-a9, but without gcc on target my work is totally unuseful.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121117/9d30a93c/attachment.html>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] gcc on target system issue
2012-11-16 21:59 ` Alexander Khryukin
@ 2012-11-17 8:10 ` Peter Korsgaard
2012-11-17 9:08 ` Alexander Khryukin
2012-11-18 13:27 ` Arnout Vandecappelle
1 sibling, 1 reply; 7+ messages in thread
From: Peter Korsgaard @ 2012-11-17 8:10 UTC (permalink / raw)
To: buildroot
>>>>> "Alexander" == Alexander Khryukin <alexander@mezon.ru> writes:
Hi,
Alexander> i'm embedded linux developer and trying to build
Alexander> OpenMandriva linux for cortex-a9, but without gcc on target
Alexander> my work is totally unuseful.
Ok, but is buildroot the right tool for that job? It would imho make
more sense to install a full blown distribution supporting ARM
(Debian/Fedora/Ubuntu/..) and use that to rebuild the mandriva packages.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] gcc on target system issue
2012-11-17 8:10 ` Peter Korsgaard
@ 2012-11-17 9:08 ` Alexander Khryukin
0 siblings, 0 replies; 7+ messages in thread
From: Alexander Khryukin @ 2012-11-17 9:08 UTC (permalink / raw)
To: buildroot
2012/11/17 Peter Korsgaard <jacmet@uclibc.org>
> >>>>> "Alexander" == Alexander Khryukin <alexander@mezon.ru> writes:
>
> Hi,
>
> Alexander> i'm embedded linux developer and trying to build
> Alexander> OpenMandriva linux for cortex-a9, but without gcc on target
> Alexander> my work is totally unuseful.
>
> Ok, but is buildroot the right tool for that job? It would imho make
> more sense to install a full blown distribution supporting ARM
> (Debian/Fedora/Ubuntu/..) and use that to rebuild the mandriva packages.
>
> --
> Bye, Peter Korsgaard
>
I want generate image for few archs like cortex a8 with hardfloat,
without, cortex-a9 with\withou, etc.
few months ago buildroot was selected as the best solution
Now i finished to adding all distro-dependent packages and trouble only
with gcc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121117/d5ec05ea/attachment.html>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] gcc on target system issue
2012-11-16 21:59 ` Alexander Khryukin
2012-11-17 8:10 ` Peter Korsgaard
@ 2012-11-18 13:27 ` Arnout Vandecappelle
1 sibling, 0 replies; 7+ messages in thread
From: Arnout Vandecappelle @ 2012-11-18 13:27 UTC (permalink / raw)
To: buildroot
On 16/11/12 22:59, Alexander Khryukin wrote:
>
>
> 2012/11/16 Thomas Petazzoni <thomas.petazzoni at free-electrons.com <mailto:thomas.petazzoni@free-electrons.com>>
>
>> Dear Alexander Khryukin,
>>
>> On Fri, 16 Nov 2012 01:20:32 +0300, Alexander Khryukin wrote:
>>
>> > I'm trying to build gcc on target but it fails with
>>
>> Why are you trying to build gcc on target? What is the purpose of
>> getting gcc on the target when building a small embedded Linux system
>> with Buildroot?
>>
>> Notice that as per the decisions taken during the last Buildroot
>> Developers Meeting, the possibility of building gcc for the target in
>> Buildroot should soon be deprecated. So there is not a strong interest
>> to fix problems reported by users.
>
>
> Ah, it bad solution to deprecate gcc on target.
Well, the problem is that it is more or less broken (as you can testify), and
that nobody is motivated to invest energy into making it work. If you find the
time and resources to fix and maintain gcc on target, and you have a relevant
use case, then there is a possibility to undeprecate it again.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2012-11-18 13:27 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-15 22:20 [Buildroot] gcc on target system issue Alexander Khryukin
2012-11-16 17:10 ` Alexander Khryukin
2012-11-16 17:30 ` Thomas Petazzoni
2012-11-16 21:59 ` Alexander Khryukin
2012-11-17 8:10 ` Peter Korsgaard
2012-11-17 9:08 ` Alexander Khryukin
2012-11-18 13:27 ` Arnout Vandecappelle
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox