GNOME Bugzilla – Bug 364368
jhbuild Makefile install flags incompatible with Solaris install
Last modified: 2006-10-23 16:51:16 UTC
Please describe the problem: The Makefile for jhbuild uses the '-m755' option to install the 'install-check' program into $(bindir). While GNU and BSD install(1) allow the omission of the space between the m option and the first digit of the octal mode, Solaris' install(1M) requires this space to be present. Steps to reproduce: 1. Find a machine running SunOS 5.11 2. cvs -d:pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co jhbuild 3. make && make install Actual results: Don't forget to create ~/.jhbuildrc install -m755 install-check /home/wheel/zanchey/bin/install-check install: -m755 was not found anywhere! make: *** [install] Error 2 Expected results: install -m 755 install-check /home/wheel/zanchey/bin/install-check install-check installed as /home/wheel/zanchey/bin/install-check Does this happen every time? Always. Other information: The following patch fixes this problem on Solaris, and does not impair use on GNU/Linux (Debian testing/unstable) or BSD (FreeBSD 6.1). RCS file: /cvs/gnome/jhbuild/Makefile,v retrieving revision 1.18 diff -u -r1.18 Makefile --- Makefile 10 Aug 2006 18:16:02 -0000 1.18 +++ Makefile 23 Oct 2006 09:45:15 -0000 @@ -28,7 +28,7 @@ @echo "Exec=$(bindir)/jhbuild gui" >> $(desktopdir)/jhbuild.desktop @[ -f $(HOME)/.jhbuildrc ]||echo "Don't forget to create ~/.jhbuildrc" - install -m755 install-check $(bindir)/install-check + install -m 755 install-check $(bindir)/install-check
Further examination of the Sun install(1M) utility shows that it accepts a limited subset of the GNU/BSD syntax. The above change will only work where an install-check file of any sort exists in the target destination. The manual page for install(1M) suggests the use of install(1B) (located in /usr/ucb for reference). This binary accepts a mode flag without a space. I am not sure what the procedure on GNOME Bugzilla is, but I think this bug should be closed INVALID or NOTABUG. Apologies for the noise.
(In reply to comment #1) > I am not sure what the procedure on GNOME Bugzilla is, but I think this bug > should be closed INVALID or NOTABUG. Okay, will do. Thanks for following up. :)