binary install file on debian

The place to post if you need help or advice

Moderators: ChrisThornett, LXF moderators

binary install file on debian

Postby guy » Tue Oct 15, 2013 11:41 am

FlightCrew is an ePub book file validator. It is available for 64-bit Linux from here, as a .bin "install file".

I never met one of those before, just rpm and deb. How do I install it on a Debian system, preferably via the desktop software tools so it gets hooked into debian's dependency management and all those good things?
"Klinger, do you know how many zoots were killed to make that one suit?" — BJ Hunnicutt
User avatar
guy
LXF regular
 
Posts: 1100
Joined: Thu Apr 07, 2005 12:07 pm
Location: Worcestershire

Postby nelz » Tue Oct 15, 2013 12:42 pm

It's an executable, like installing to Windows with an .exe file.

Code: Select all
chmod +x FlightCrew-0.7.2-Linux-x86_64-Setup.bin
./FlightCrew-0.7.2-Linux-x86_64-Setup.bin


preferably via the desktop software tools so it gets hooked into debian's dependency management and all those good things?


You don't, the package manager won't know about it because it's an executable, like installing to Windows with an .exe file :(

You could try filing a package request on your distro's bug tracker.
"Insanity: doing the same thing over and over again and expecting different results." (Albert Einstein)
User avatar
nelz
Site admin
 
Posts: 8552
Joined: Mon Apr 04, 2005 11:52 am
Location: Warrington, UK

Postby guy » Tue Oct 15, 2013 3:53 pm

nelz wrote:It's an executable, like installing to Windows with an .exe file.

Code: Select all
chmod +x FlightCrew-0.7.2-Linux-x86_64-Setup.bin
./FlightCrew-0.7.2-Linux-x86_64-Setup.bin




guy@hostname:~/Downloads$ chmod -x FlightCrew-0.7.2-Linux-x86_64-Setup.bin
guy@hostname:~/Downloads$ ./FlightCrew-0.7.2-Linux-x86_64-Setup.bin
bash: ./FlightCrew-0.7.2-Linux-x86_64-Setup.bin: Permission denied

:(

Do I need to sudo or move it to somewhere magic or what?
"Klinger, do you know how many zoots were killed to make that one suit?" — BJ Hunnicutt
User avatar
guy
LXF regular
 
Posts: 1100
Joined: Thu Apr 07, 2005 12:07 pm
Location: Worcestershire

Postby nelz » Tue Oct 15, 2013 4:07 pm

chmod +x, not chmod -x

You need to add executable permission, not remove it.

As to whether it needs root permissions to run, you'll have to try it. I'd try as a normal user first, in which case it will either install to your home directory or complain about needing root permissions.
"Insanity: doing the same thing over and over again and expecting different results." (Albert Einstein)
User avatar
nelz
Site admin
 
Posts: 8552
Joined: Mon Apr 04, 2005 11:52 am
Location: Warrington, UK

Postby roseway » Tue Oct 15, 2013 6:05 pm

I don't know whether this will work, but you might try using checkinstall:

checkinstall FlightCrew-0.7.2-Linux-x86_64-Setup.bin

Checkinstall works by wrapping up the installation files in a .deb or .rpm package, depending on the host system.
Eric
roseway
LXF regular
 
Posts: 450
Joined: Thu Jan 18, 2007 2:27 pm

Postby guy » Tue Oct 15, 2013 6:16 pm

nelz wrote:chmod +x, not chmod -x

D'oh! I knew that! :oops:

Now installed.
"Klinger, do you know how many zoots were killed to make that one suit?" — BJ Hunnicutt
User avatar
guy
LXF regular
 
Posts: 1100
Joined: Thu Apr 07, 2005 12:07 pm
Location: Worcestershire

Postby guy » Wed Oct 16, 2013 4:18 pm

Installed but baffling. It installed a desktop icon which launches the gui: /home/guy/flightcrew/flightcrew-gui.sh

But clicking the icon or running flightcrew-gui.sh directly has no visible effect, i.e. no gui gets launched that I can see. Tried from bash and got:
Code: Select all
guy@hostname:~/flightcrew$ ./flightcrew-gui.sh
/home/guy/flightcrew/./flightcrew-gui: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by /home/guy/flightcrew/./flightcrew-gui)


Here is the contents of flightcrew-gui.sh:

Code: Select all
#!/bin/sh

# Entry point for FlightCrew-gui on Unix systems.
# Adds the directory the FlightCrew-gui executable is located
# in to the LD_LIBRARY_PATH so the custom Qt libs
# are recognized and loaded.

appname=`basename $0 | sed s,\.sh$,,`

dirname=`dirname $0`
tmp="${dirname#?}"

if [ "${dirname%$tmp}" != "/" ]; then
dirname=$PWD/$dirname
fi
LD_LIBRARY_PATH=$dirname
export LD_LIBRARY_PATH
#if no agruments are passed then call just FlightCrew-gui program; else pass arguments.
if [$* == ""]
then
$dirname/$appname
else
#argument may not be pass correctly without qoutation marks.
$dirname/$appname "$*"
fi


I use Gnome2, so am I right in thinking this is the gates of QT dependency hell? Or is there an easy way?
"Klinger, do you know how many zoots were killed to make that one suit?" — BJ Hunnicutt
User avatar
guy
LXF regular
 
Posts: 1100
Joined: Thu Apr 07, 2005 12:07 pm
Location: Worcestershire

Postby nelz » Wed Oct 16, 2013 4:22 pm

It's far more serious than that, it wants a different version of glibc from what you have running.
"Insanity: doing the same thing over and over again and expecting different results." (Albert Einstein)
User avatar
nelz
Site admin
 
Posts: 8552
Joined: Mon Apr 04, 2005 11:52 am
Location: Warrington, UK

Postby guy » Wed Oct 16, 2013 4:40 pm

Okaay, I think I'll wait for the Wright brothers to fix it. Many thanks, anyway.
"Klinger, do you know how many zoots were killed to make that one suit?" — BJ Hunnicutt
User avatar
guy
LXF regular
 
Posts: 1100
Joined: Thu Apr 07, 2005 12:07 pm
Location: Worcestershire


Return to Help!

Who is online

Users browsing this forum: No registered users and 0 guests