From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] ucilbc 0.9.33.2 fails to build on buildroot 2013.11 internal toolchain
Date: Sat, 30 Nov 2013 22:46:52 +0100 [thread overview]
Message-ID: <529A5CCC.3000803@mind.be> (raw)
In-Reply-To: <20131128192508.4c4c0106@skate>
On 28/11/13 19:25, Thomas Petazzoni wrote:
> Dear Alexander Varnin,
>
> On Thu, 28 Nov 2013 21:55:08 +0400, Alexander Varnin wrote:
>
>> Building uclibc with default config now fails for me, after upgrading
>> to latest buildroot (now from 2013.11-rc3 branch).Attaching my config.
>> Build system is Debian Wheezy.
>>
>> Here is short output of make command:
>>
>> varnin at debian5 ~/minipos-OS-build-2013.11> make
>> make -C /home/varnin/buildroot
>> O=/home/varnin/minipos-OS-build-2013.11/.
>>>>> uclibc 0.9.33.2 Building
>> /usr/bin/make -j1 -C
>> /home/varnin/minipos-OS-build-2013.11/build/uclibc-0.9.33.2 ARCH="arm"
>> CROSS_COMPILE="/home/varnin/minipos-OS-build-2013.11/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-"
>> UCLIBC_EXTRA_CFLAGS=" " HOSTCC="/usr/bin/gcc" PREFIX= DEVEL_PREFIX=/
>> RUNTIME_PREFIX=/ all
>> make[3]: Nothing to be done for `locale_headers'.
>> LD libuClibc-0.9.33.2.so
>> libc/libc_so.a(lockf.os): In function `__GI_lockf':
>> /home/varnin/minipos-OS-build-2013.11/build/uclibc-0.9.33.2/libc/misc/file/lockf.c:73:
>> undefined reference to `_Unwind_Resume'
>> libc/libc_so.a(lockf.os):(.ARM.extab+0x0): undefined reference to
>> `__gcc_personality_v0'
>> collect2: error: ld returned 1 exit status
>> make[2]: *** [lib/libc.so] ?????? 1
>> make[1]: ***
>> [/home/varnin/minipos-OS-build-2013.11/build/uclibc-0.9.33.2/.stamp_built]
>> ?????? 2
>> make: *** [_all] ?????? 2
>
> My guess is that you have BR2_ENABLE_DEBUG=y in your Buildroot .config,
> right?
>
> If that's the case, then you've hit the problem that uClibc doesn't
> build properly when debugging support is enabled. That's unfortunately
> an upstream uClibc problem, I believe.
>
> Either disable BR2_ENABLE_DEBUG in Buildroot (which will disable
> debugging support for all packages), or if you want to keep debugging
> support enabled globally but don't care about debugging support in
> uClibc, apply a change like:
>
> diff --git a/package/uclibc/uclibc.mk b/package/uclibc/uclibc.mk
> index 20d3bb6..062ac0d 100644
> --- a/package/uclibc/uclibc.mk
> +++ b/package/uclibc/uclibc.mk
> @@ -390,14 +390,6 @@ UCLIBC_WCHAR_CONFIG = $(call UCLIBC_OPT_UNSET,UCLIBC_HAS_WCHAR,$(@D))
> endif
>
> #
> -# debug
> -#
> -
> -ifeq ($(BR2_ENABLE_DEBUG),y)
> -UCLIBC_DEBUG_CONFIG = $(call UCLIBC_OPT_SET,DODEBUG,y,$(@D))
> -endif
> -
> -#
So why not apply this patch in buildroot?
Regards,
Arnout
> # strip
> #
>
> Best regards,
>
> Thomas
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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
next prev parent reply other threads:[~2013-11-30 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 17:55 [Buildroot] ucilbc 0.9.33.2 fails to build on buildroot 2013.11 internal toolchain Alexander Varnin
2013-11-28 18:25 ` Thomas Petazzoni
2013-11-28 21:34 ` Alexander Varnin
2013-11-30 21:46 ` Arnout Vandecappelle [this message]
2013-11-28 18:27 ` Peter Korsgaard
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=529A5CCC.3000803@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.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