Re: [Chromium-users] gm and chromium in AMD64 land

[Mike H. <mho...@gr...>]

If you have GM support for X86_64, then you must be running the GM-2 
code.  I don't think all of the required API changes for GM-2 have made 
it into the Chromium tree.  Also, the default GM installation should 
place the header and library files in /usr in the correct places, so you 
shouldn't need to copy them across unless you don't have a system wide 
installation.

If things go awry, you might want to try Sockets-GM (IP over GM).

-Mike

Sam Liston wrote:

> Both gm and Chromium build fine independantly under Redhat ES 4 Beta 
> (2.6 kernel), but when I try to build Chromium with GM_SUPPORT ( I put 
> the gm.h and libgm.a in the chromiumdir/utils ) I get the following 
> error:
>
> ------------------------------------------------------------------------------- 
>
>              Building libcrutil.so for Linux (RELEASE) (THREADSAFE)
> ------------------------------------------------------------------------------- 
>
> Compiling bbox.c
> Compiling bufpool.c
> Compiling devnull.c
> Compiling dll.c
> Compiling endian.c
> Compiling environment.c
> Compiling error.c
> Compiling filenet.c
> Compiling hash.c
> Compiling hull.c
> Compiling list.c
> Compiling matrix.c
> Compiling mem.c
> Compiling net.c
> Compiling pixel.c
> Compiling process.c
> Compiling rand.c
> Compiling string.c
> Compiling threads.c
> Compiling tcpip.c
> Compiling udptcpip.c
> Compiling timer.c
> Compiling url.c
> Compiling warp.c
> Compiling gm.c
> Linking ../built/crutil/Linux/libcrutil.so
> /usr/bin/ld: 
> /uufs/skylinearch.chpc.utah.edu/host/pkg/cr/std/util/libgm.a(gm_dma_malloc.o): 
> relocation R_X86_64_32 against `a local symbol' can not be used when 
> making a shared object; recompile with -fPIC
> /uufs/skylinearch.chpc.utah.edu/host/pkg/cr/std/util/libgm.a: could 
> not read symbols: Bad value
> collect2: ld returned 1 exit status
> gmake[1]: *** [../built/crutil/Linux/libcrutil.so] Error
> make: *** [dep] Error 2
>
> Any ideas?  Has the method for building with GM_SUPPORT changed, or is 
> this and Architecture issue?
> Thanks,
> Sam
>