From owner-freebsd-ports Sun Feb 10 15:28:39 2002 Delivered-To: freebsd-ports@freebsd.org Received: from reynoldsnet.org (ip68-2-87-144.ph.ph.cox.net [68.2.87.144]) by hub.freebsd.org (Postfix) with ESMTP id 6DA9437B400 for ; Sun, 10 Feb 2002 15:28:34 -0800 (PST) Received: from whale.home-net (whale [192.168.1.2]) by reynoldsnet.org (8.11.6/8.11.6) with ESMTP id g1ANSXx68771 for ; Sun, 10 Feb 2002 16:28:33 -0700 (MST) (envelope-from johnjen@reynoldsnet.org) Received: (from jjreynold@localhost) by whale.home-net (8.11.6/8.11.6) id g1ANSTb20209; Sun, 10 Feb 2002 16:28:29 -0700 (MST) (envelope-from johnjen@reynoldsnet.org) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15463.541.192355.507243@whale.home-net> Date: Sun, 10 Feb 2002 16:28:29 -0700 To: ports@freebsd.org Subject: problem building ghostcript-gnu if gimp-print installed X-Mailer: VM 6.88 under Emacs 20.7.1 Cc: Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, the last several times I've built ghostscript-gnu from the ports, I've had to work around the following error when it builds the gimp-print GS drivers: if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \ XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \ FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \ DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \ DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \ DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \ DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \ /bin/sh <./obj/ldt.tr /usr/local/lib/libgimpprint.so: undefined reference to `dgettext' /usr/local/lib/libgimpprint.so: undefined reference to `bindtextdomain' gmake: *** [bin/gs] Error 1 *** Error code 2 Stop in /usr/ports/print/ghostscript-gnu. *** Error code 1 Stop in /usr/ports/print/ghostscript-gnu. *** Error code 1 Stop in /usr/ports/print/ghostscript-gnu. I have /usr/local/lib/libgimpprint.so installed because I'm using gimp-print's drivers with CUPS for printing to my Epson 980. In order to get ghostscript-gnu to compile, I have to temporarily move the libgimpprint.so and .a files out of that directory and then move them back after ghostscript-gnu builds. Does anybody else see this? If the file (underneath "work") ./obj/ldt.tr is modified to not have /usr/local/lib as the first -L option like so: cc -L./obj/ -L/usr/local/lib -fno-common -o ./bin/gs ./obj/gs.o ./obj/gp_getnv.o \ the build proceeds as the libgimpprint.a file that is symlinked into the "obj" directory is picked up for linking rather than the one in /usr/local/lib. I believe the following patch to unixlink.mak fixes the problem (I just verified that this is the case with a fresh compile). Can we get this committed as a "local FreeBSD" patch? I'm in the process of hacking up a port which will go in conjuction with the CUPS port to bring in the wonderful Gimp-print CUPS drivers, and with this (currently vaporware) port installed, building ghostscript-gnu will die unless the attached patch isn't in place. Thanks, -Jr --- unixlink.mak.orig Sun Feb 10 16:20:29 2002 +++ unixlink.mak Sun Feb 10 16:22:27 2002 @@ -64,7 +64,7 @@ # which has limited environment space. ldt_tr=$(PSOBJ)ldt.tr $(GS_XE): $(ld_tr) $(ECHOGS_XE) $(XE_ALL) - $(ECHOGS_XE) -w $(ldt_tr) -n - $(CCLD) $(LDFLAGS) -o $(GS_XE) + $(ECHOGS_XE) -w $(ldt_tr) -n - $(CCLD) -L$(PSOBJ) $(LDFLAGS) -o $(GS_XE) $(ECHOGS_XE) -a $(ldt_tr) -n -s $(PSOBJ)gs.$(OBJ) -s cat $(ld_tr) >>$(ldt_tr) $(ECHOGS_XE) -a $(ldt_tr) -s - $(EXTRALIBS) $(STDLIBS) -- John & Jennifer Reynolds johnjen@reynoldsnet.org http://www.reynoldsnet.org/ Senior CAD Engineer, WCCG, Intel Corporation jreynold@sedona.ch.intel.com Running FreeBSD since 2.1.5-RELEASE. FreeBSD: The Power to Serve! "Unix is user friendly, it's just particular about the friends it chooses." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message