From owner-freebsd-ports Mon Nov 18 18:47:33 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA08238 for ports-outgoing; Mon, 18 Nov 1996 18:47:33 -0800 (PST) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA08227 for ; Mon, 18 Nov 1996 18:47:28 -0800 (PST) Received: from professor.eng.umd.edu (professor.eng.umd.edu [129.2.103.23]) by po1.glue.umd.edu (8.8.2/8.7.3) with ESMTP id VAA05771; Mon, 18 Nov 1996 21:47:15 -0500 (EST) Received: from localhost (chuckr@localhost) by professor.eng.umd.edu (8.8.3/8.7.3) with SMTP id VAA14706; Mon, 18 Nov 1996 21:47:15 -0500 (EST) X-Authentication-Warning: professor.eng.umd.edu: chuckr owned process doing -bs Date: Mon, 18 Nov 1996 21:47:14 -0500 (EST) From: Chuck Robey X-Sender: chuckr@professor.eng.umd.edu To: Joerg Wunsch cc: pgiffuni@fps.biblos.unal.edu.co, ports@freebsd.org Subject: Re: Are broken ports useful? In-Reply-To: <199611190057.BAA03940@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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! ----------------------------+-----------------------------------------------