>>> Brian Paul <brian.paul@...> 01/30/04 03:07PM >>>
Daniel Rawson wrote:
> I'm trying to build Mesa under Solaris with the following setup:
> Solaris 9 for x86
> Latest "Recommended" patch cluster
> gcc v3.3.2
> The libraries compile fine; the lib directory looks like:
> -rwxr-xr-x 1 rawsond staff 2746440 Jan 30 12:33 libGL.so
> -rwxr-xr-x 1 rawsond staff 596148 Jan 30 12:33 libGLU.so
> -rwxr-xr-x 1 rawsond staff 343824 Jan 30 12:33 libglut.so
> -rwxr-xr-x 1 rawsond staff 14684 Jan 30 12:33 libGLw.so
> -rwxr-xr-x 1 rawsond staff 53024 Jan 30 12:33 libOSMesa.so
> However, the demos fail to compile:
> gcc -I../../include -O3 -m486 -fPIC -I/usr/openwin/include -DUSE_XSHM a=
rbfplight.c -L../../lib -L/usr/openwin/lib -R/usr/openwin/lib -lX11 -lXex=
t -lXmu -lXi -lm -o arbfplight
> `-m486' is deprecated. Use `-march=3Di486' or `-mcpu=3Di486' instead.
> Undefined=09=09=09first referenced
> symbol =09=09=09 in file
> glutIdleFunc /var/tmp//cc8def0Z.o
> glViewport /var/tmp//cc8def0Z.o
> glEnable /var/tmp//cc8def0Z.o
> glGetError /var/tmp//cc8def0Z.o
> glDisable /var/tmp//cc8def0Z.o
> glutCreateWindow /var/tmp//cc8def0Z.o
> Running elfdump on the libraries DOES show the relevant symbols. I als=
o tried turning off -O3 (by modifying Make-config)
> Any hints would be appreciated . .. .
Which version of Mesa are you using?
How are you building Mesa?
I'm building version 6.0 by running "make solaris-x86-gcc" from the top l=
evel . . .
I just tried another experiment which seems to have fixed this for the de=
mos directory; I add the Mesa libraries to the dependency lines in progs/=
demos/Makefile.X11 as follows:
MESA_LIBS=3D-lgut -lGL -lGLU -lOSMesa
$(CC) -I$(INCDIR) $(CFLAGS) $< $(LIBS) $(MESA_LIBS) -o $@
I'm using GNU make 3.79.1. I didn't see any place in the makefiles or Ma=
ke-config where the additional libraries are called out, but the demos ob=
viously need to link against them . . .
Software Configuration Management
The information contained in this communication and any attachments is co=
nfidential and may be privileged, and is for the sole use of the intended=
recipient(s). Any unauthorized review, use, disclosure or distribution i=
s prohibited. If you are not the intended recipient, please notify the se=
nder immediately by replying to this message and destroy all copies of th=
is message and any attachments. ASML is neither liable for the proper and=
complete transmission of the information contained in this communication=
, nor for any delay in its receipt.