d'oh! Too early in the morning for me.

On Mon, Nov 11, 2013 at 9:49 AM, Jasper St. Pierre <jstpie...@mecheye.net>wrote:

> That's an error for glibc, not glib. You'd be better off talking to the
> glibc people about that one...
>
>
> On Mon, Nov 11, 2013 at 12:32 PM, Daniel Schultze <king...@gmail.com>wrote:
>
>> Hey guys,
>>
>> I'm have a new error with my build. I did some searches which suggested
>> to not use --enable-static-nss which I'm not doing. I did do an edit to one
>> of the awk scripts, scripts/gen-sorted.awk, the build was reporting an
>> error on lines containing /\/[^/]+$/ , so I added an extra backslash in the
>> middle to /\/[^\/]+$/ . Hopefully this edit is unrelated.
>>
>> Here's the error log:
>> isoc99_scanf.c: In function '__isoc99_scanf':
>> isoc99_scanf.c:33: error: '_IO_acquire_lock_needs_exceptions_enabled'
>> undeclared (first use in this function)
>> isoc99_scanf.c:33: error: (Each undeclared identifier is reported only
>> once
>> isoc99_scanf.c:33: error: for each function it appears in.)
>> isoc99_scanf.c: At top level:
>> isoc99_scanf.c:40: error: expected identifier or '(' before 'while'
>> isoc99_scanf.c:41: error: expected identifier or '(' before 'return'
>> isoc99_scanf.c:42: error: expected identifier or '(' before '}' token
>> make[2]: ***
>> [/home/xxx/ltib_xx/rpm/BUILD/glibc-2.7/build-glibc/stdio-common/isoc99_scanf.o]
>> Error 1
>> make[2]: *** Waiting for unfinished jobs....
>> isoc99_vscanf.c: In function '__isoc99_vscanf':
>> isoc99_vscanf.c:29: error: '_IO_acquire_lock_needs_exceptions_enabled'
>> undeclared (first use in this function)
>> isoc99_vscanf.c:29: error: (Each undeclared identifier is reported only
>> once
>> isoc99_vscanf.c:29: error: for each function it appears in.)
>> isoc99_vscanf.c: At top level:
>> isoc99_vscanf.c:32: error: expected identifier or '(' before 'while'
>> isoc99_vscanf.c:33: error: expected identifier or '(' before 'return'
>> isoc99_vscanf.c:34: error: expected identifier or '(' before '}' token
>> make[2]: ***
>> [/home/xxx/ltib_xx/rpm/BUILD/glibc-2.7/build-glibc/stdio-common/isoc99_vscanf.o]
>> Error 1
>> isoc99_fscanf.c: In function '__isoc99_fscanf':
>> isoc99_fscanf.c:31: error: '_IO_acquire_lock_needs_exceptions_enabled'
>> undeclared (first use in this function)
>> isoc99_fscanf.c:31: error: (Each undeclared identifier is reported only
>> once
>> isoc99_fscanf.c:31: error: for each function it appears in.)
>> isoc99_fscanf.c: At top level:
>> isoc99_fscanf.c:38: error: expected identifier or '(' before 'while'
>> isoc99_fscanf.c:39: error: expected identifier or '(' before 'return'
>> isoc99_fscanf.c:40: error: expected identifier or '(' before '}' token
>> make[2]: ***
>> [/home/xxx/ltib_xx/rpm/BUILD/glibc-2.7/build-glibc/stdio-common/isoc99_fscanf.o]
>> Error 1
>> isoc99_vfscanf.c: In function '__isoc99_vfscanf':
>> isoc99_vfscanf.c:29: error: '_IO_acquire_lock_needs_exceptions_enabled'
>> undeclared (first use in this function)
>> isoc99_vfscanf.c:29: error: (Each undeclared identifier is reported only
>> once
>> isoc99_vfscanf.c:29: error: for each function it appears in.)
>> isoc99_vfscanf.c: At top level:
>> isoc99_vfscanf.c:32: error: expected identifier or '(' before 'while'
>> isoc99_vfscanf.c:33: error: expected identifier or '(' before 'return'
>> isoc99_vfscanf.c:34: error: expected identifier or '(' before '}' token
>> make[2]: ***
>> [/home/xxx/ltib_xx/rpm/BUILD/glibc-2.7/build-glibc/stdio-common/isoc99_vfscanf.o]
>> Error 1
>> make[2]: Leaving directory
>> `/home/xxx/ltib_xx/rpm/BUILD/glibc-2.7/stdio-common'
>> make[1]: *** [stdio-common/subdir_lib] Error 2
>> make[1]: Leaving directory `/home/xxx/ltib_xx/rpm/BUILD/glibc-2.7'
>> make: *** [all] Error 2
>> error: Bad exit status from /home/xxx/ltib_xx/tmp/rpm-tmp.15860 (%build)
>>
>>
>> -Dan
>>
>>
>> On Fri, Nov 8, 2013 at 12:01 PM, Colin Walters <walt...@verbum.org>wrote:
>>
>>> On Fri, 2013-11-08 at 10:28 -0800, Daniel Schultze wrote:
>>>
>>>
>>> > The host is Ubuntu 12.04 x86_64, the target CPU is an arm926ejs on a
>>> > Freescale board, using LTIB. It is an older system using glibc 2.5
>>> > with glibc ports 2.5.
>>>
>>> From a quick look, this commit to glibc looks like it updated the splice
>>> prototype:
>>>
>>> commit 99ea5991a4957f7a21466a4b48c5020eb70db2b7
>>> Author:     Ulrich Drepper <drep...@redhat.com>
>>> AuthorDate: Wed Aug 30 15:05:29 2006 +0000
>>>
>>>     * sysdeps/unix/sysv/linux/alpha/bits/fcntl.h (splice): Add offin
>>>
>>> Which as you can see is really quite ancient.
>>>
>>> > --- glib-2.28.7.orig/configure 2011-05-20 21:15:25.000000000 -0700
>>> > +++ glib-2.28.7/configure 2013-11-08 10:15:51.380683520 -0800
>>> > @@ -23107,7 +23107,6 @@
>>> >    ac_fn_c_check_func "$LINENO" "splice" "ac_cv_func_splice"
>>> >  if test "x$ac_cv_func_splice" = xyes; then :
>>> >    cat >>confdefs.h <<_ACEOF
>>> > -#define HAVE_SPLICE 1
>>> >  _ACEOF
>>>
>>> That's probably fine as a fix for you for now, this issue will go away
>>> when you update to a version of glibc from this decade too =)
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> gtk-devel-list mailing list
>> gtk-devel-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/gtk-devel-list
>>
>>
>
>
> --
>   Jasper
>
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list

Reply via email to