I'd like to report that in unifdef.c there are three instances for getline, which I changed to parseline, the def, the function and the one use of it. And it now has compiled that part and is moving, just in case others have this issue it's now documented, hopefully this will make it into svn as it is backward compat to old libcs as well so it won't break on previously working setups.
Chaos is the beginning and end, try dealing with the rest.
On 2010-01-22, at 10:05 AM, TheSin wrote:
> looks like this is an issue for rawhide too and they fixed it by renaming that call
> Is svn still updated, should this get fixed in svn?
> Chaos is the beginning and end, try dealing with the rest.
> On 2010-01-22, at 9:17 AM, TheSin wrote:
>> Hi guys I'm sorry if this has been answered a lot but I've tried google for 2 days now.
>> I'm running Debian Squeezy (testing) and setup my bitbake area to make new rootfs'
>> I'm guessing the newer libc in Squeezy is the issue.
>> ii libc6 2.10.2-2 GNU C Library: Shared libraries
>> But I can't run bitbake I keep getting
>> NOTE: package unifdef-native-2.6.18+git: started
>> NOTE: package unifdef-native-2.6.18+git-r0: task do_compile: started
>> ERROR: function do_compile failed
>> ERROR: log data follows (/home/justin/gumstix/gumstix-oe/tmp/work/i686-linux/unifdef-native-2.6.18+git-r0/temp/log.do_compile.18803)
>> | /home/justin/gumstix/gumstix-oe/tmp/work/i686-linux/unifdef-native-2.6.18+git-r0/unifdef.c:209: error: conflicting types for 'getline'
>> | /usr/include/stdio.h:651: error: previous declaration of 'getline' was here
>> NOTE: Task failed: /home/justin/gumstix/gumstix-oe/tmp/work/i686-linux/unifdef-native-2.6.18+git-r0/temp/log.do_compile.18803
>> NOTE: package unifdef-native-2.6.18+git-r0: task do_compile: failed
>> Does anyone have a qemu image with an env for bitbaking?
>> I'm running into even worst issues with buildroot on Debian Squeezy or OSX, It's very frustrating having a project almost done but I can't make a clean jffs2, anyhelp is greatly greatly appreciated, I'm assume the bitbake way will be the easiest.
>> Chaos is the beginning and end, try dealing with the rest.