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: > > ######################## > beast:/usr/ports/print/ghostscript-gnu # setenv TARGET_ARCH=i386 > beast:/usr/ports/print/ghostscript-gnu # make -DWITHOUT_X11 -DBATCH > ... > gmake[2]: Entering directory >`/usr/ports/print/ghostscript-gnu/work/ghostscript-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/ghostscript-7.05/gimp-print-4.2.1' > gmake[1]: Leaving directory >`/usr/ports/print/ghostscript-gnu/work/ghostscript-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= -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 > > Stop in /usr/ports/print/ghostscript-gnu. > beast:/usr/ports/print/ghostscript-gnu # > ######################## > 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, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age
msg41293/pgp00000.pgp
Description: PGP signature