Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 May 2008 07:58:28 -0500
From:      "Scot Hetzel" <swhetzel@gmail.com>
To:        "Andy Fawcett" <andy@athame.co.uk>
Cc:        "Aryeh M. Friedman" <aryeh.friedman@gmail.com>, freebsd-ports@freebsd.org, "Sean C. Farley" <scf@freebsd.org>
Subject:   Re: problems building the latest ghostscript-gpl
Message-ID:  <790a9fff0805080558g3eb1d6edj7eb9697a876ebf8c@mail.gmail.com>
In-Reply-To: <200805072023.24933.andy@athame.co.uk>
References:  <48215E7E.90505@gmail.com> <200805071840.51141.andy@athame.co.uk> <alpine.BSF.1.10.0805071137570.1154@thor.farley.org> <200805072023.24933.andy@athame.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
I'm also having the same problem building on
FreeBSD/AMD64 8-CURRENT.  I commented out the entries
I had in ports.conf for this port, and checked CFLAGS:

# cd /usr/ports/print/ghostscript-gpl
# make -V CFLAGS
-O2 -pipe  -fno-strict-aliasing

And the port fails the same way.  FT_BRIDGE is not enabled.  When I added -fPIC
to CFLAGS_STANDARD.  Then the port would build.

Scot

On 5/7/08, Andy Fawcett <andy@athame.co.uk> wrote:
> On Wednesday 07 May 2008 19:42:31 Sean C. Farley wrote:
>> On Wed, 7 May 2008, Andy Fawcett wrote:
>> > On Wednesday 07 May 2008 17:13:59 Sean C. Farley wrote:
>> >> On Wed, 7 May 2008, Aryeh M. Friedman wrote:
>> >>> /usr/bin/ld: ./obj/../soobj/gs.o: relocation R_X86_64_32 can not be
>> >>> used when making a shared object; recompile with -fPIC
>> >>
>> >> On amd64, you need to remove the FT_BRIDGE option to compile.  I have
>> >> not had time to look into what is actually happening or needs to be
>> >> fixed.
>> >
>> > Makes no difference here, I get the same error with:
>> >
>> > _OPTIONS_READ=ghostscript-gpl-8.62_1
>> > WITHOUT_FONTCONFIG=true
>> > WITHOUT_FT_BRIDGE=true
>> > WITHOUT_GS_lvga256=true
>> > WITHOUT_GS_vgalib=true
>> > .
>> > .
>> > all other items are WITH_foo=true
>>
>> That is what I have.  Maybe a rebuild of freetype2 (v2.3.5 here) would
>> help?  Are you using a port builder that sets the environment variable
>> BATCH and have portconf installed?  That may bypass the setting in the
>> options file.  Those are my only guesses.
>
> I'm using portupgrade, BATCH is not set, portconf isn't installed, and all
> dependency ports are up to date. This is with a csup just before I sent the
> mail, so pretty up to date.
>
> Andy
>
>
>
>
> --
> Andy Fawcett                                     | andy@athame.co.uk
>                                                  | tap@kde.org
> "In an open world without walls and fences,      | tap@lspace.org
>   we wouldn't need Windows and Gates."  -- anon  | tap@fruitsalad.org
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0805080558g3eb1d6edj7eb9697a876ebf8c>