Re: Accidentally installed libtool wrapper scripts instead of binaries

2016-07-14 Thread Richard W.M. Jones
On Thu, Jul 14, 2016 at 05:20:41PM +0200, Pavel Raiskup wrote: > I doubt installed wrapper script worked for you; but yes - it might be too > late as not everything is manually tested (if not detected by toolchain). It fails quite dramatically ... $ libguestfs-boot-benchmark mkdir: cannot create

Re: Accidentally installed libtool wrapper scripts instead of binaries

2016-07-14 Thread Pavel Raiskup
On Wednesday, July 13, 2016 2:27:11 PM CEST Richard W.M. Jones wrote: > Just a note more than anything, since I don't see this problem > discussed anywhere in the packaging guidelines ... > [...] > I accidentally packaged some libtool wrapper scripts by doing: It probably rarely happens as the 'ma

Re: Accidentally installed libtool wrapper scripts instead of binaries

2016-07-14 Thread Richard W.M. Jones
On Thu, Jul 14, 2016 at 09:52:20AM +0200, Igor Gnatenko wrote: > Good point, but how do we know if file is libtool wrapper and not real > shell-script? If you're happy with a heuristic, then they should be easy to identify from the comments at the very beginning of the file, which look like below.

Re: Accidentally installed libtool wrapper scripts instead of binaries

2016-07-14 Thread Igor Gnatenko
Good point, but how do we know if file is libtool wrapper and not real shell-script? On Wed, Jul 13, 2016 at 3:27 PM, Richard W.M. Jones wrote: > Just a note more than anything, since I don't see this problem > discussed anywhere in the packaging guidelines ... > > If a package uses libtool, then

Accidentally installed libtool wrapper scripts instead of binaries

2016-07-13 Thread Richard W.M. Jones
Just a note more than anything, since I don't see this problem discussed anywhere in the packaging guidelines ... If a package uses libtool, then sometimes libtool generates bash scripts instead of executables. These libtool wrapper scripts can be run from the build directory and run the real exe