#319 Files installed to bin without execute bit set

Jason Lenz

I'm in the process of creating a "HomeBrew" formula for compiling source on OSX. The install system provides a warning that files are installed to the bin directory without the execute bit set. It also provides a warning that non library files were installed to lib. See below for the files in question. I'm no expert on this but they seem like good warnings with the possible exception of the ".jnilib" warnings. Thanks much.
--------Output from my custom "HomeBrew" formula below--------------
==> Build Environment
CPU: quad-core 64-bit sandybridge
MacOS: 10.7.3-x86_64
Xcode: 4.3.2
CC: /usr/bin/clang
CXX: /usr/bin/clang++ => /usr/bin/clang
LD: /usr/bin/clang
CFLAGS: -Os -w -pipe -march=native -Qunused-arguments
CXXFLAGS: -Os -w -pipe -march=native -Qunused-arguments
==> Downloading http://downloads.sourceforge.net/sourceforge/brlcad/brlcad-7.20.4.tar.gz
==> ./autogen.sh
==> ./configure --enable-almost_everything --enable-optimized --disable-debug --prefix=/usr/local/Cellar/brlcad/7.20.4
==> make install
Warning: Non-executables were installed to "bin".
Installing non-executables to "bin" is bad practice.
The offending files are:
Warning: Non-libraries were installed to "lib".
Installing non-libraries to "lib" is bad practice.
The offending files are:
==> Summary
/usr/local/Cellar/brlcad/7.20.4: 3790 files, 147M, built in 9.9 minutes


  • Jason Lenz

    Jason Lenz - 2012-03-25
    • priority: 5 --> 3
  • Sean Morrison

    Sean Morrison - 2012-03-27
    • assigned_to: nobody --> brlcad
    • status: open --> pending-out-of-date
  • Sean Morrison

    Sean Morrison - 2012-03-27

    So two Issues. First, all of the warnings are either intentional, false positive, or out of our control. Second and more importantly, it looks like you're using our old build system. We are transitioning to a cmake-based build. The same build options are available but specified differently.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks