Re: [Gumstix-users] New buildroot directory structure

[Grahame J. <gb...@th...>]

Hi,

 I am compileing this on AMD64 but I am in 32bit mode.  I compiled this 
OK on a 32bit platform.
I think the problem is associated with

-D_FILE_OFFSET_BITS=64

Where is this set so I can unset it :)

Thanks

Grahame Jordan




Grahame Jordan wrote:

>Hi,
>
>I am having trouble builging at Compiling sysfs_class.c: 
>
>Running a default .config
>
>Complaining about:
>Unfortunately, uClibc was built without large file support enabled.
>
>  /home/gjordan/gumstix/br2/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-gc
>  c -c -g -Wall -pipe -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -Wstrict-prototypes
>  -Wsign-compare -Wshadow -Wchar-subscripts -Wmissing-declarations 
>-Wnested-ext
>  erns -Wpointer-arith -Wcast-align -Wsign-compare -Wmissing-prototypes -Os 
>-I/
>  home/gjordan/gumstix/br2/build_arm_nofpu/udev-079/libsysfs/sysfs 
>-I/home/gjor
>  dan/gumstix/br2/build_arm_nofpu/udev-079/libsysfs libsysfs/sysfs_class.c -o 
>l
>  ibsysfs/sysfs_class.o
>  In file included 
>from /home/gjordan/gumstix/br2/build_arm_nofpu/staging_dir/l
>  
>ib/gcc/arm-linux-uclibc/3.4.4/../../../../arm-linux-uclibc/sys-include/sys/ty
>  pes.h:26,
>                   
>from /home/gjordan/gumstix/br2/build_arm_nofpu/udev-079/libs
>  ysfs/sysfs/libsysfs.h:26,
>                   from libsysfs/sysfs_class.c:23:
>  /home/gjordan/gumstix/br2/build_arm_nofpu/staging_dir/lib/gcc/arm-linux-uclib
>  c/3.4.4/../../../../arm-linux-uclibc/sys-include/features.h:329:2: #error It
>  appears you have defined _FILE_OFFSET_BITS=64. Unfortunately, uClibc was 
>buil
>  t without large file support enabled.
>
>
>
>Thanks
>
>Grahame Jordan
>
>On Fri, 17 Feb 2006 19:57, Craig Hughes wrote:
>  
>
>>I just finished a mammoth effort to get all the gumstix stuff ported
>>to the new buildroot directory structure (for some definition of
>>"new").  I've got it all working now in http://svn.gumstix.com/
>>gumstix-buildroot/branches/projects/br2 and intend to merge onto the
>>trunk ASAP.  I've tested the main bits of functionality by building a
>>u-boot and root_fs and both seem to work (note that root_fs_arm_nofpu
>>is now named rootfs.arm_nofpu.jffs2).
>>
>>Other than that, everything's heavily moved around, and the buildroot
>>itself now has a nice "make menuconfig" option for turning packages
>>on and off and stuff.  Each package lives in its own separate
>>directory, including .mk file, Config.in file for the config system,
>>and patches (if any).  The top level structure now looks like:
>>
>>.
>>
>>|-- docs        [documentation]
>>|-- package     [.mk, Config.in and patches for all the packages
>>
>>which can be installed]
>>
>>|-- target      [.mk, Config.in and patches for things specific to a
>>
>>particular target platform; linux is included in here for some reason]
>>
>>|-- toolchain   [.mk, Config.in and patches for the cross-compiler
>>
>>tools (binutils, gcc, uClibc, etc)
>>
>>|-- build_arm_nofpu   [stuff gets built in this directory, as before]
>>|
>>|    |-- staging_dir  [stuff is "installed" here for use on the build
>>
>>host]
>>
>>|    `-- root         [stuff is "installed" here and will then become
>>
>>the root_fs for the target system]
>>`-- toolchain_build_arm_nofpu   [stuff gets built in this directory,
>>as before]
>>
>>If you're familiar with the old buildroot, this should be pretty easy
>>to figure out, with the possible exception of the fine semantics of
>>what goes in target vs package vs toolchain -- it seems somewhat
>>arbitrary in places.
>>
>>anyhoo, if some of the more adventurous among you would be willing to
>>try out the new SVN branch and see if it is in fact working right
>>(including any pet packages you might want to try out), please do so
>>and let me know.
>>
>>If nobody much complains that things are horribly broken in the next
>>couple of days, I'll merge onto the trunk and update all the various
>>wiki pages which talk about how the buildroot works.
>>
>>Thanks,
>>
>>C
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: Splunk Inc. Do you grep through log
>>files for problems?  Stop!  Download the new AJAX search engine that makes
>>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
>>_______________________________________________
>>gumstix-users mailing list
>>gum...@li...
>>https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>    
>>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
>_______________________________________________
>gumstix-users mailing list
>gum...@li...
>https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>  
>