> | 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scot Hetzel wrote:
| 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
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 enabl
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 m
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
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.
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
On May 7, 2008, at 2:15 AM, Aryeh M. Friedman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Garrett Cooper wrote:
| On May 7, 2008, at 1:05 AM, Aryeh M. Friedman wrote:
|
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> Garrett Cooper wrote:
|
| [...]
|
|> | Aryeh,
|> | What
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Garrett Cooper wrote:
| On May 7, 2008, at 1:05 AM, Aryeh M. Friedman wrote:
|
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> Garrett Cooper wrote:
|
| [...]
|
|> | Aryeh,
|> | What are your CFLAGS?
|>
|> If you mean the ones from /etc/
On May 7, 2008, at 1:05 AM, Aryeh M. Friedman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Garrett Cooper wrote:
[...]
| Aryeh,
| What are your CFLAGS?
If you mean the ones from /etc/make.conf:
CPUTYPE?=nocona
KERNCONF=MONSTER
NO_LPR=true
NO_PROFILE=true
NO_CLEAN=true
# added
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Garrett Cooper wrote:
| On May 7, 2008, at 12:47 AM, Aryeh M. Friedman wrote:
|
| Using the default options I get the following when attempting to
rebuild the latest version of print/ghostscript-gpl on 8-CURRENT (AMD64):
|
| cc -DHAVE_MKSTEMP -DHAV
On May 7, 2008, at 12:47 AM, Aryeh M. Friedman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Using the default options I get the following when attempting to
rebuild the latest version of print/ghostscript-gpl on 8-CURRENT
(AMD64):
cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Using the default options I get the following when attempting to rebuild
the latest version of print/ghostscript-gpl on 8-CURRENT (AMD64):
cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFIG -O2 -pipe
-march=nocona -fno-strict-aliasing -DUPD_SIGN
13 matches
Mail list logo
