Date: Wed, 24 Jul 2002 14:50:45 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: John Hay <jhay@icomtek.csir.co.za> Cc: portmgr@FreeBSD.org, current@FreeBSD.org, Makoto Matsushita <matusita@FreeBSD.org> Subject: Re: setting TARGET_ARCH breaks ghostscript in make release Message-ID: <20020724115045.GB29635@sunbay.com> In-Reply-To: <200207241059.g6OAxA610207@zibbi.icomtek.csir.co.za> References: <200207241059.g6OAxA610207@zibbi.icomtek.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
--lEGEL1/lMxI0MVQ2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jul 24, 2002 at 12:59:10PM +0200, John Hay wrote:
> It looks like the change in release/Makefile to add TARGET_ARCH breaks
> the build of ghostscript-gnu. Actually just setting the TARGET_ARCH
> environment variable and then trying to build print/ghostscript-gnu
> will break:
>=20
> ########################
> beast:/usr/ports/print/ghostscript-gnu # setenv TARGET_ARCH=3Di386
> beast:/usr/ports/print/ghostscript-gnu # make -DWITHOUT_X11 -DBATCH
> ...
> gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghost=
script-7.05/gimp-print-4.2.1'
> gmake[2]: Nothing to be done for `all-am'.
> gmake[2]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghosts=
cript-7.05/gimp-print-4.2.1'
> gmake[1]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghosts=
cript-7.05/gimp-print-4.2.1'
> >>> creating symlinks for gimp-print ...
> >>> creating symlinks for md2k ...
> >>> creating symlinks for alps ...
> >>> creating symlinks for bj10v ...
> >>> creating symlinks for lips ...
> >>> building epag utility ...
> cc -O -pipe i386=3D -c -o ert.o ert.c
> cc: cannot specify -o with -c or -S and multiple compilations
> gmake: *** [ert.o] Error 1
> *** Error code 2
>=20
> Stop in /usr/ports/print/ghostscript-gnu.
> beast:/usr/ports/print/ghostscript-gnu #
> ########################
>=20
One possible work-around might be to fix doc.1 to use ${NATIVEMAKE}.
But the actual problem, as you have noticed, is with bsd.port.mk.
I think it should provide a clean environment (with /usr/bin/env -i)
when building a port. This would also fix the problem. I'm copying
portmgr@ therefore.
PS. Why haven't you Cc:ed this to me?
Cheers,
--=20
Ruslan Ermilov Sysadmin and DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
--lEGEL1/lMxI0MVQ2
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)
iD8DBQE9PpSVUkv4P6juNwoRAjlBAJ4oJKB70rU3BoyyWxELRk7c1zVeAQCeMbW4
UoKhD4flQgojyJCwXgrTfhU=
=oOO4
-----END PGP SIGNATURE-----
--lEGEL1/lMxI0MVQ2--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020724115045.GB29635>