[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gcl-devel] " *** [raw_gcl_map] Error 1" happens while making GCL

From: Wolfgang Pichl
Subject: Re: [Gcl-devel] " *** [raw_gcl_map] Error 1" happens while making GCL
Date: Fri, 24 Jul 2009 14:55:17 +0200 (CEST)
User-agent: Alpine 2.00 (LNX 1167 2008-08-23)

On Thu, 23 Jul 2009, address@hidden wrote:

I encounter the problem while making GCL.

My system is Redhat enterprise 5 and GCL version is gcl-2.6.7

I am struggling this problem for 2 days. Please someone can help me to solve 
this problem.


***** The errors is the following  
gcc -o raw_gcl  \
               -L.  -Wl,-Map raw_gcl_map   -lgcl -lm  /usr/lib64/libbfd.a 
/usr/lib64/libiberty.a -lc -lgclp
./libgcl.a(sys_gcl.o): In function `gcl_init_system':
sys_gcl.c:(.text+0x35bd): undefined reference to `init_gcl_cmpwt'
sys_gcl.c:(.text+0x363a): undefined reference to `init_gcl_predlib'
sys_gcl.c:(.text+0x36b7): undefined reference to `init_gcl_setf'
sys_gcl.c:(.text+0x3734): undefined reference to `init_gcl_assert'

did you use the 2.6.7 release tarball or a Fedora srpm? I've compiled gcl on Slackware and Slamd64 a few weeks ago and thereby learned that the 2.6.7 tarball does not compile out of the box. You'll at least need several patches and probably you'll also have to do some manual hacks in the configure script and turn off brk randomization in the Linux kernel. In the Fedora source rpms these issues seem to be fixed, but I don't know for certain, I'm not a Fedora user. Probably the best thing you could do is to try the 2.6.8-pre prerelease; it worked out of the box for me. You'll have to check it out from the cvs, it has not yet been released.

In case that 2.6.8-pre also should not work for you, here a few other points that might be helpful: Did you use a parallel make (e.g. make -j4 or something like that) ? Whith the current versions of binutils this fails whenever static libraries are to be built (ar builds corrupted libraries within a parallel make). And you are definitly having a problem with a static library, so this might be an indication...

You are obviously using a 64bit "multilib" distribution. If problems persist, make sure that the distribution setup (compiler and linker internal paths, dynamic loader...) is correct and libraries in locations as /usr/lib64 and /usr/local/lib64 are correctly found. AFAIK, 64bit Fedora should be clean, as Slamd64 is, but I don't know for sure. Some distributions (e.g. Gentoo) are notorious for their bad 64bit-multilib-setup.

best regards
Wolfgang Pichl

reply via email to

[Prev in Thread] Current Thread [Next in Thread]