Bump minimum glibc version to 2.3.3

Any complaints about doing this? The changes involve:

• change source:apbuild/trunk/buildlist to filter only 2.4 and above
• rebuild source:apbuild/trunk/apsymbols.h
• change source:main/trunk/makepackage to scan for 2.4 and above

Any others?

rebuilt filtering greater than 2.3.3

The attachment glibc-2.3.3.diff contains a new buildlist script that should filter all symbols above glibc 2.3.3. Unfortunately, I don't know if I changed everything correctly as some of the comments were a little unclear to me. If someone else could take a look at the changes (and the resulting apsymbols.h, also in the patch), and confirm that it looks correct, that would be great.

FYI, the GlibcVersionsOfDifferentLinuxDistributions page shows what versions of glibc shipped with different versions of distros.

This patch does also make this one obvious. Would be cool if it could be committed before 1.3, but unfortunately I don't understand a single line, so I can't confirm that everything is correct.

Regarding the patch.. the following awk code will not do what we want it to do:

awk ' { if ($2 > 2.3.3) ...

If quoted (to force string comparison) it will work better, but it'll break for version numbers larger than 9 (e.g. "1.2.10", "1.10.0", "10.12.13" etc)

New patch, which uses 2.3 and therefore isn't affected by the comparision bug descriped by Isak

Unfortunately the apsymbols.h of my patch doesn't work, I can't compile anything.

New patch: Remove dups from apsymbols.h, add ChangeLog entry

jhasse: try the new patch. There were dups in the symbol file. I just removed them but I'm not sure why they were there in the first place...

New patch works fine! Can we commit it?

I've just committed it in r2505.

Blimey! I'm getting this error in Ubuntu 8.04.1 32 Bit when compiling autopackage:

apgcc -std=gnu99 -Wall -Wfloat-equal -Wmissing-noreturn -O2 -march=i586 -pipe -export-dynamic  
-o mkapspec mkapspec-apspec.o mkapspec-main.o mkapspec-utils.o mkapspec-binreloc.o mkapspec-
mainwin.o mkapspec-mainwin_cb.o mkapspec-dialogs_cb.o mkapspec-dialogs.o -lglade-2.0 -lgtk-
x11-2.0 -lxml2 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo 
-lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0    
mkapspec-binreloc.o: In function `gbr_init_lib':
binreloc.c:(.text+0x5e0): undefined reference to `__isoc99_sscanf@GLIBC_DONT_USE_THIS_SYMBOL'
binreloc.c:(.text+0x623): undefined reference to `__isoc99_sscanf@GLIBC_DONT_USE_THIS_SYMBOL'
/usr/bin/ld: mkapspec: No symbol version section for versioned symbol 
`__isoc99_sscanf@GLIBC_DONT_USE_THIS_SYMBOL'
/usr/bin/ld: final link failed: Nonrepresentable section on output

Replying to Jan-Nik:

Blimey! I'm getting this error in Ubuntu 8.04.1 32 Bit when compiling autopackage: {{{ binreloc.c:(.text+0x5e0): undefined reference to `isoc99_sscanf@GLIBC_DONT_USE_THIS_SYMBOL' }}}

Fixed in r2509 for mkapspec. But the bigger problem is still there:

in glibc 2.7, this new symbol isoc99_sscanf and a few friends was added as a compile time drop-in replacement for the normal sscanf. So any program compiled on a glibc > 2.7 system which uses any of the scanf functions and is compiling with the --std=c99 gcc option will be hit by this :-(

The bad thing is: binreloc.c is calling sscanf in one of its functions (this is what I removed from mkapspec) so basically all autopackaged software will be hit by this one. We could fix binreloc by replacing the sscanf usage with strtoul(start, end, 16); which should have the same effect but it has some 32 vs 64 bit issues we need to handle first.

Okay, I've created a new ticket for the C99 problem (#100) and close this one as fixed.