[opensource-dev] BUG-1610: Current development source does not build with glibc 2.17

2013-02-09 Thread Lance Corrimal
hi, does anyone have anything for me about fixing up the source to build with glibc 2.17? I'm getting ready for openSUSE 12.3 here, and that uses the newer glibc... for details, see BUG-1610 cheers, LC ___ Policies and (un)subscribe information

Re: [opensource-dev] BUG-1610: Current development source does not build with glibc 2.17

2013-02-09 Thread Nicky Perian
https://bitbucket.org/NickyP/kokua-3.4.4/commits/22012aa8388a38fb657113b0db3effcfdaa3a8d9 From: Lance Corrimal lance.corri...@eregion.de To: opensource-dev@lists.secondlife.com Sent: Saturday, February 9, 2013 4:13 AM Subject: [opensource-dev] BUG-1610:

Re: [opensource-dev] BUG-1610: Current development source does not build with glibc 2.17

2013-02-09 Thread Lance Corrimal
Thanks... I haven't even gotten that far, my build died way earlier, with a conflicting declaration for siginfo_t, but I got that tackled now. cheers, LC Am Samstag, 9. Februar 2013, 02:34:09 schrieb Nicky Perian: https://bitbucket.org/NickyP/kokua-3.4.4/commits/22012aa8388a38fb657113b0db3

Re: [opensource-dev] BUG-1610: Current development source does not build with glibc 2.17

2013-02-09 Thread Nicky Perian
Would you mark BUG-1610 as a duplicate of OPEN-164? From: Lance Corrimal lance.corri...@eregion.de To: opensource-dev@lists.secondlife.com Sent: Saturday, February 9, 2013 5:00 AM Subject: Re: [opensource-dev] BUG-1610: Current development source does not

Re: [opensource-dev] BUG-1610: Current development source does not build with glibc 2.17

2013-02-09 Thread Lance Corrimal
Am Samstag, 9. Februar 2013, 04:41:10 schrieb Nicky Perian: Would you mark BUG-1610 as a duplicate of OPEN-164? definitely not. the problem that I had is because glibc 2.17 brings the siginfo_t definition by itself... definitely something else. What I'd think suitable would be a meta bug that

Re: [opensource-dev] BUG-1610: Current development source does not build with glibc 2.17

2013-02-09 Thread Lance Corrimal
This is where I'm stuck now: [ 363s] /home/abuild/rpmbuild/BUILD/viewer-development/build-linux- i686/lscript/lscript_compile/indra.y.hpp:176: error: previous declaration of 'int yyparse()' with 'C++' linkage [ 363s] /home/abuild/rpmbuild/BUILD/viewer-

Re: [opensource-dev] BUG-1610: Current development source does not build with glibc 2.17

2013-02-09 Thread Cinder Roxley
Lance, I use a workaround on OSX Mountain Lion which fails with the same error, and it might work for you too. Patch attached and as follows: START--- # HG changeset patch # User Cinder Roxley cin...@cinderblocks.biz # Date 1360441583 25200 #

Re: [opensource-dev] BUG-1610: Current development source does not build with glibc 2.17

2013-02-09 Thread Cinder Roxley
Here's a better fix than the other one I posted earlier… Don't use extern C. START- diff --git a/indra/lscript/lscript_compile/indra.l b/indra/lscript/lscript_compile/indra.l --- a/indra/lscript/lscript_compile/indra.l +++ b/indra/lscript/lscript_compile/indra.l @@

Re: [opensource-dev] BUG-1610: Current development source does not build with glibc 2.17

2013-02-09 Thread Argent Stonecutter
On 2013-02-09, at 15:40, Cinder Roxley cin...@cinderblocks.biz wrote: Here's a better fix than the other one I posted earlier… Don't use extern C. That... shouldn't work, unless it's generating C++ code in lex/yacc/bison/whatever. ___ Policies and