This looks like something I saw last week.  Using 'make
linux-dri-x86-64' instead of 'make linux-dri' worked for me.

I think this also created a /usr/X11R7/lib64 directory.  I moved the two
files in it to /usr/X11R7/lib and created a link called lib64 that
points to lib.  I'm still building CLFS, but I haven't had any problems
with this yet.  

On Thu, 2006-12-14 at 17:52 -0800, Janis Stipins wrote:
> Hi,
> 
> I've followed the CLFS-1.0.0 directions to build a pure 64-bit
> xf86_64 linux installation on my AMD64 machine.  So far,
> everything has worked beautifully without a hitch...
> 
> ...until I tried to build MesaLib-6.5.  I have been following the
> directions for Xorg7 on the CBLFS wiki... the Utility Macros,
> Protocol Headers, Libraries, and libdrm all installed without
> a problem.  But when I try to build MesaLib-6.5, the following
> error occurs:
> 
> makedepend -fdepend -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L
> -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DPTHREADS
> -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING
> -DHAVE_ALIAS -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
> -I../../../../../../drm/shared-core -I../../../../../include
> -I../../../../../include/GL/internal -I../../../../../src/mesa
> -I../../../../../src/mesa/main -I../../../../../src/mesa/glapi
> -I../../../../../src/mesa/math -I../../../../../src/mesa/transform
> -I../../../../../src/mesa/shader -I../../../../../src/mesa/swrast
> -I../../../../../src/mesa/swrast_setup -I../../../../../src/egl/main
> -I../../../../../src/egl/drivers/dri  `pkg-config --cflags
> libdrm` ../../common/driverfuncs.c ../common/utils.c ../common/texmem.c 
> ../common/vblank.c ../common/dri_util.c ../common/xmlconfig.c 
> ../common/drirenderbuffer.c ffb_bitmap.c ffb_clear.c ffb_dd.c ffb_depth.c 
> ffb_fog.c ffb_lines.c ffb_points.c ffb_span.c ffb_state.c ffb_stencil.c 
> ffb_tex.c ffb_tris.c ffb_vb.c ffb_xmesa.c  \
>                 >& /dev/null
> gcc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
> -I../../../../../../drm/shared-core -I../../../../../include
> -I../../../../../include/GL/internal -I../../../../../src/mesa
> -I../../../../../src/mesa/main -I../../../../../src/mesa/glapi
> -I../../../../../src/mesa/math -I../../../../../src/mesa/transform
> -I../../../../../src/mesa/shader -I../../../../../src/mesa/swrast
> -I../../../../../src/mesa/swrast_setup -I../../../../../src/egl/main
> -I../../../../../src/egl/drivers/dri  `pkg-config --cflags libdrm`
> -Wall -Wmissing-prototypes -g -fPIC  -D_POSIX_SOURCE
> -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE
> -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER
> -DGLX_DIRECT_RENDERING -DHAVE_ALIAS  -std=c99 -ffast-math
> -D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE
> -D_GNU_SOURCE -DPTHREADS -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER
> -DGLX_DIRECT_RENDERING -DHAVE_ALIAS ffb_lines.c -o ffb_lines.o
> ../../../../../bin/mklib -noprefix -o ffb_dri.so \
>                 ../../common/driverfuncs.o ../common/utils.o 
> ../common/texmem.o ../common/vblank.o ../common/dri_util.o 
> ../common/xmlconfig.o ../common/drirenderbuffer.o ffb_bitmap.o ffb_clear.o 
> ffb_dd.o ffb_depth.o ffb_fog.o ffb_lines.o ffb_points.o ffb_span.o 
> ffb_state.o ffb_stencil.o ffb_tex.o ffb_tris.o ffb_vb.o ffb_xmesa.o   
> ../../../../../src/mesa/libmesa.a  -L/usr/X11R7/lib -lm -lpthread -lexpat 
> -ldl `pkg-config --libs libdrm`
> mklib: Making Linux shared library:  ffb_dri.so
> /usr/bin/ld: ffb_lines.o: relocation R_X86_64_PC32 against `ffb_line'
> can not be used when making a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: Bad value
> collect2: ld returned 1 exit status
> install ffb_dri.so ../../../../../lib
> install: cannot stat `ffb_dri.so': No such file or directory
> make: *** [../../../../../lib/ffb_dri.so] Error 1
> 
> 
> This is strange, because it looks to me like ffb_lines.c was compiled 
> with the -fPIC flag.  Also, the shared libraries in the other driver
> subdirectories were created with no problem, so it doesn't seem 
> like lack of -fPIC is the real problem.
> 
> Has anybody else had this issue?  Any wisdom or suggestions would
> be very much appreciated.
> 
> Thanks,
> -Janis
> 
> 
> 
> 
> ______________________________________________________________________
> Have a burning question? Go to Yahoo! Answers and get answers from
> real people who know.
> _______________________________________________
> Clfs-support mailing list
> [email protected]
> http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support

_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support

Reply via email to