This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
thank you for the hint. Now that I let crosstool unpack and patch the sources all goes well and I have got a wonderful crosscompiler :-)
Mike Frysinger wrote:
On Friday 18 March 2005 05:30 am, Friedhelm Wolf wrote:
/usr/local/crosstool-0.28-rc37/build/i686-pc-linux-gnu/gcc-3.3.3-glibc-2.3.
2/build-glibc/stdio-common/sscanf.o sscanf.c:31: warning: conflicting types
for built-in function `sscanf' sscanf.c: In function `sscanf':
sscanf.c:37: error: `va_start' used in function with fixed args
../stdio-common/_itoa.h: At top level:
../stdio-common/_itoa.h:40: warning: inlining failed in call to
`_itoa_word' ../stdio-common/_itoa.h:76: warning: called from here
make[2]: ***
it's been a while since ive seen/fixed this, but if iirc, you just have to touch up the prototype in sscanf.c a bit to make it happy
a little google search for that error turned up this: http://sources.redhat.com/bugzilla/show_bug.cgi?id=132
It's a known problem, not cygwin-specific.
In fact, crosstool has a fix for it in
http://kegel.com/crosstool/crosstool-0.28-rc37/patches/glibc-2.3.2/sscanf.patch
but since you didn't let crosstool unpack sources, it didn't apply the patch.
Maybe you should let crosstool build from tarballs, it'll avoid a lot of trouble. - Dan
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |