[Linux]-[BMAX 1.30 rev 1.61]-libc.so.6 issue

BlitzMax Forums/BlitzMax Bug Reports/[Linux]-[BMAX 1.30 rev 1.61]-libc.so.6 issue

Hi,

after updated to rev 1.61, i received :

U /home/flaith/1-Programs/BlitzMax1.30/mod/brl.mod/blitz.mod/blitz_app.c
U /home/flaith/1-Programs/BlitzMax1.30/src/bmk/bmk_util.bmx
Actualisé à la révision 161.

U /home/flaith/1-Programs/BlitzMax1.30/bin/makedocs
U /home/flaith/1-Programs/BlitzMax1.30/bin/docmods
U /home/flaith/1-Programs/BlitzMax1.30/bin/bmk
Actualisé à la révision 161.

but after a bmk makemods :

./bin/bmk: /lib/tls/i686/cmov/libc.so.6: version `GLIBC_2.4' not found (required by ./bin/bmk)

I'm under Debian Etch with libc6-i386 version 2.3.6.ds1-13etch7

Thanks for your help

skidracer

not an uncommon problem for linux binary distributors, this guy has found a possible solution which we may be able to use, although there is an not 4 ubuntu link at the bottom which makes pretty sad reading:

http://gbgames.com/blog/2008/04/linux-game-development-glibc_24-errors-solved/

flaith

Thanks for the link skidracer, going to read it ... and pray to fine a solution to my problem

flaith

Am i the only one to have this issue ?
I still cannot compile any program :(

#Reaper

Hi,
I also have had (my english is bad...btw) this problem. I dont solved it. I just went back to revision 151, then it works again. Maybe the new reivison 164 is working fine, but I havent it tested jet.

#Reaper

flaith

Hi #Reaper, i've just updated to rev 164 (thread), no change.
How did you downgrade to previous revision ?

#Reaper

Hi,
in command-line:
svn update -r 151
(then only it downgraded the lib-folder, I dont know why only this) or
svn update -r 151 bin
for the bin-folder only.
I hope it works :)

greetings
#Reaper

flaith

thanks for the info

After downgrading to revision 151, a bmk makemods has given a

Command line error

:(

But now i can compile my programs

thanks #Reaper :)

** EDIT ***********
Same pb with rev 166
******************

#Reaper

no problem :)

I was able to compile the mods with rev 151.
Are you sure that you used it correct? (I forget every time how to use... ;) )
The docu says:

The makemods operation builds a set of modules.

Makemods takes one optional argument: a module filter. This can be a module scope name (to build a subset of modules) or a fully qualified module name (to build an individual module). If the module filter is omitted, than all module are built.

Valid options for makemods are: Option Effect
-d Build debug version. By default, both debug and release versions are built.
-r Build release version. By default, both debug and release versions are built.
-a Build all modules regardless of timestamps. By default, only modules that have been modified are built.

Some examples of makemods in action:

bmk makemods mymods
bmk makemods -a mymods.testmod

So you could try
bmk makemods -a
to rebuild all mods. I hope that works. :)
But maybe (I dont know) you dont need to rebuild all mods if you downgraded..?

greetings
#Reaper
:-)

flaith

#10

bmk makemods -a

perfect, it's ok, for now ;)

Thanks again #Reaper :D