From owner-freebsd-ports Mon Nov 18 21:57:18 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA17820 for ports-outgoing; Mon, 18 Nov 1996 21:57:18 -0800 (PST) Received: from ingenieria ([168.176.15.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA17815 for ; Mon, 18 Nov 1996 21:57:15 -0800 (PST) Received: from unalmodem.usc.unal.edu.co by ingenieria (SMI-8.6/SMI-SVR4) id AAA28194; Tue, 19 Nov 1996 00:56:14 +0600 Message-ID: <329175B4.476C@ingenieria.ingsala.unal.edu.co> Date: Tue, 19 Nov 1996 00:54:41 -0800 From: "Pedro Giffuni S." Reply-To: pgiffuni@fps.biblos.unal.edu.co Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 3.0 (Win16; I) MIME-Version: 1.0 To: Chuck Robey CC: Joerg Wunsch , ports@freebsd.org Subject: Re: Are broken ports useful? References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks to both, It has much sense to modify the Makefile.in instead of the Makefile, for one thing I donīt know exactly what will come out after configuring (specially if an OpenBSD dude wants to try it). I checked into the Makefile.in and found this (among other things): INSTALL = @INSTALL@ INSTALL_PROGRAM = @INSTALL_PROGRAM@ INSTALL_DATA = @INSTALL_DATA@ INSTALL_USER = @USER@ on the Makefile I found this: INSTALL = /usr/bin/install -c -o bin -g bin INSTALL_PROGRAM = /usr/bin/install -c -s -o bin -g bin -m 555 What do I look for? What must I change? (it's my first port!) Pedro. Chuck Robey wrote: > > On Tue, 19 Nov 1996, J Wunsch wrote: > > > As pgiffuni@fps.biblos.unal.edu.co wrote: > > > > > I have a port for cim, a simula compiler, it compiles great and the test > > > script runs OK, but when I try to install it the script fails when it is > > > going to strip it due to "wrong format". > > > I am using fbsd 2.1.5, with the old gcc, should I leave it like this to > > > see if it works under 2.2, or should I remove the strip portion from the > > > makefile? > > > > The latter. It has been decided (back in time) that using -s when > > trying to install a script executable is considered a usage error, > > hence install fails in this situation. > > You're right, Joerg, but I am not sure it's completely valid, because I've > hit this error before (albeit not in the cim compiler, so it would bear > doublechecking). The problem has been, in the past, that the gnu-written > install script is using INSTALL_BINARY to install scripts. INSTALL_BINARY > (as I'm sure you'll agree) should be -s, but in a lot of gnu stuff, the > authors misuse the install variables. If you look in the generated > Makefiles, it's there real clearly. The right fix has been, for me, to > patch the Makefile.in file so that the right macros are used to install > scripts. I really wouldn't want to muff error checking in install for > this reason. > > I have one glaring example in mind, but I can't remember the name right > now. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 9120 Edmonston Ct #302 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+-----------------------------------------------