From vangyzen@stat.duke.edu  Wed Feb 19 01:05:03 2003
From: vangyzen@stat.duke.edu (Eric van Gyzen)
Date: Wed Feb 19 01:05:03 2003
Subject: [Rd] R won't compile on FreeBSD 5.0 (PR#2562)
In-Reply-To: <15954.49790.675775.532175@mithrandir.hornik.net>
References: <200302182224.h1IMOF35003678@pubhealth.ku.dk> <x27kbx9o5j.fsf@biostat.ku.dk> <15954.49790.675775.532175@mithrandir.hornik.net>
Message-ID: <200302181904.03943.vangyzen@stat.duke.edu>

Kurt Hornik wrote:
> >>>>> Peter Dalgaard BSA writes:
> >
> > vangyzen@stat.duke.edu writes:
> >> Full_Name: Eric van Gyzen
> >> Version: 1.6.2
> >> OS: FreeBSD 5.0-RELEASE i386
> >> Submission from: (NULL) (152.3.22.120)
> >>
> >>
> >> When compiling R (versions 1.6.1 and 1.6.2), I get the following
> >> messages: dumping R code in package 'methods'
> >> Fatal error: The X11 shared library could not be loaded.
> >> The error was /tmp/R-1.6.2/modules/R_X11.so: Undefined symbol
> >> "R_GlobalEnv"
> >>
> >> The compiler is GCC 3.2.1.  I'll be glad to provide more information via
> >> email.
> >>
> >> Thanks in advance for any help!
> >
> > Hmm. You might need to get a FreeBSD expert in on this. I guess that
> > it is not the methods package that has the problem; that is just the
> > first time anything tries to run the newly built R binary. R_GlobalEnv
> > is defined in R.bin so the problem is that the dyn.load mechanism is
> > not able to resolve this. A bit of Google'ing suggests that a
> > -export-dynamic (or so) flag might have fallen out of the link command
> > for R.bin.

Aha!  That would explain the rather terse dynamic symbol table in R.bin...

> Actually ... the configure code has
>
>   freebsd[3-4].*)
>     main_ldflags="-export-dynamic"
>     shlib_ldflags="-shared"
>     ;;
>
> so does not cover freebsd5 --- maybe this should be changed?

Yep.  Changing the range from 3-4 to 3-5 fixed it.

Thanks for the fast, accurate help, gentlemen.

Eric



[Rd] R won't compile on FreeBSD 5.0 (PR#2562)
Eric van Gyzen