[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: #error "This file assumes that 'int' has exactly 32 bits.

From: Eric Blake
Subject: Re: #error "This file assumes that 'int' has exactly 32 bits.
Date: Fri, 09 Aug 2013 07:59:44 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7

[re-adding the list, with permission]

On 08/09/2013 07:35 AM, I Love To Get Spamed wrote:
> Hello Eric,
> Thanks for the response.

[please don't top-post on technical lists - reformatting your reply]

>> Thanks for the report, but it is incomplete.  You reported your compiler
>> (arm-angstrom-linux-gnueabi-gcc), but not necessarily your platform.
>> Given the compiler, is this an attempted cross-compile?  What sizes does
>> your compiler assign to the basic types?  Is this more a bug of
>> cross-compilation getting wrong guesses rather than actually having a
>> non-32-bit int?  Can you show config.log snippets around the area of the
>> failure?

> I'm trying to use the Angstrom-distribution bitbake recipies to compile a
> distro for a beaglebone black.  my host computer is Ubuntu (uname -a
> Linux epic-dev02 3.5.0-37-generic #58~precise1-Ubuntu SMP Wed Jul 10
> 17:48:11 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux)

Okay, so you are definitely cross-compiling.  Now, can you give us more
details about the "beaglebone black" system that you are targetting, as
I am unfamiliar with it.  What size integers does it use?

> Chris
> the build log is as flows:
> DEBUG: Executing shell function do_compile
> NOTE: make -j2

You pasted the (huge) output of the bitbake script, that is not what I
asked for.  I want the portion of the config.log that shows what was
attempted during configure when probing for bit sizes of 'int'.
Trimming your paste somewhat to fit within mailing list limits of 100k

> gcc -std=gnu99
> -isystem/home/epic/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/sysroots/x86_64-linux/usr/include
> -O2 -pipe
> -L/home/epic/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/sysroots/x86_64-linux/usr/lib
> -L/home/epic/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/sysroots/x86_64-linux/lib
> -Wl,-rpath-link,/home/epic/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/sysroots/x86_64-linux/usr/lib
> -Wl,-rpath-link,/home/epic/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/sysroots/x86_64-linux/lib
> -Wl,-rpath,/home/epic/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/sysroots/x86_64-linux/usr/lib
> -Wl,-rpath,/home/epic/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/sysroots/x86_64-linux/lib
> -Wl,-O1 -o bison AnnotationList.o InadequacyList.o LR0.o Sbitset.o assoc.o
> closure.o complain.o conflicts.o derives.o files.o getargs.o gram.o lalr.o
> ielr.o location.o main.o muscle-tab.o named-ref.o nullable.o output.o
> parse-gram.o print.o print_graph.o print-xml.o reader.o reduce.o relation.o
> scan-code-c.o scan-gram-c.o scan-skel-c.o state.o symlist.o symtab.o
> tables.o uniqstr.o graphviz.o ../lib/libbison.a
> make[3]: Leaving directory

...This shows that you are successfully building quite a bit of the
bison package; I thought you were hitting a configure failure, but it
appears that you are instead hitting a compile failure...

> `/home/epic/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/x86_64-linux/bison-native/2.7-r1/build'
> make[1]: Leaving directory
> `/home/epic/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/x86_64-linux/bison-native/2.7-r1/build'
> DEBUG: Shell function do_compile finished

...and yet here, things finished successfully.  In your huge log, I
didn't see ANY sign of the failure that you reported originally.  I'm
not interested in what went right, but more details about what went
wrong.  Is it something you can reproduce on a smaller scale?

Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]