Gerald Pfeifer gerald at
Mon Feb 15 19:22:25 UTC 2010

On Mon, 15 Feb 2010, b. f. wrote:
> Normally, such an rpath directive would automatically be issued, but
> our lang/gcc4* ports have this default feature disabled unless
> WITHOUT_JAVA is defined, citing an old PR related to gcj and it's
> libraries:
> .if ! defined(WITHOUT_JAVA)
> ...
> # FIXME: we are currently getting weird build failures with libjava on
> # some 4.x and 5.x systems, which the following works around. PR 81788.
> CONFIGURE_ARGS+=--disable-rpath
> ...
> Someone should investigate, to see if this problem still exists.  If
> it doesn't, then we could restore the default behavior, and remove the
> corresponding statements from

Yes, the problem with Java still exists, I reproduced it on a test
system a few weeks ago.  It's hard to grasp, and I have failed to
nail it down, since outside of the FreeBSD Ports Collection, just
building from upstream SVN, everything works just fine.

That said, I do not think this is relevant here since GCC does not 
actually set an rpath as you have it in mind by default (or at all).
And least not that I'd know, or I'd use that. ;-)


More information about the freebsd-ports mailing list