Installing tar.bz2 with no .configure but with Makefile in it
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I downloaded targui from sourceforge and it comes in a tar.bz2 archive with no .configure and no instructions regarding install. However, the archive contains a Makefile.
Looking at the Makefile (and what little documentation on sourcefourge) looks like the only dependencies are qt4, which are installed on my system at /usr/share/qt4, as the Makefile seems to require.
What am I supposed to do in order to install this package ?
Link to the sourceforge page:
https://sourceforge.net/projects/targui/
UPDATE
The Makefile has this comment:
#
Makefile for building: targui
Generated by qmake (2.01a) (Qt 4.3.2) on: Fr Dez 28 12:32:13 2007
Project: targui.pro
Template: app
Command: /usr/bin/qmake -unix -o Makefile targui.pro
#
So, from within the directory containing the targui folder I tried:
/usr/bin/qmake -unix -o Makefile targui.pro
but terminal says:
qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file or directory
UPDATE 2
Built according to NOorbert instructions. It segfaults
Fixed mainwindow.cpp so now it looks like:
void MainWindow::TabChanged(int i)
if (newAct) newAct->setEnabled(i > 0);
if (openAct) openAct->setEnabled(i > 0);
if (saveAct) saveAct->setEnabled(i > 0);
if (saveAsAct) saveAsAct->setEnabled(i > 0);
and changed the tar references to /bin in the same file
.targui still segfaults
software-installation compiling make
add a comment |Â
up vote
3
down vote
favorite
I downloaded targui from sourceforge and it comes in a tar.bz2 archive with no .configure and no instructions regarding install. However, the archive contains a Makefile.
Looking at the Makefile (and what little documentation on sourcefourge) looks like the only dependencies are qt4, which are installed on my system at /usr/share/qt4, as the Makefile seems to require.
What am I supposed to do in order to install this package ?
Link to the sourceforge page:
https://sourceforge.net/projects/targui/
UPDATE
The Makefile has this comment:
#
Makefile for building: targui
Generated by qmake (2.01a) (Qt 4.3.2) on: Fr Dez 28 12:32:13 2007
Project: targui.pro
Template: app
Command: /usr/bin/qmake -unix -o Makefile targui.pro
#
So, from within the directory containing the targui folder I tried:
/usr/bin/qmake -unix -o Makefile targui.pro
but terminal says:
qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file or directory
UPDATE 2
Built according to NOorbert instructions. It segfaults
Fixed mainwindow.cpp so now it looks like:
void MainWindow::TabChanged(int i)
if (newAct) newAct->setEnabled(i > 0);
if (openAct) openAct->setEnabled(i > 0);
if (saveAct) saveAct->setEnabled(i > 0);
if (saveAsAct) saveAsAct->setEnabled(i > 0);
and changed the tar references to /bin in the same file
.targui still segfaults
software-installation compiling make
I got the binary to build but it segfaults immediately on execution; do you still want to know the steps I followed?
â dsstorefile1
Aug 20 at 10:49
Yes please, maybe I got better luck...
â Gumbo
Aug 20 at 11:03
I got around the segfault, see below.
â dsstorefile1
Aug 20 at 11:45
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I downloaded targui from sourceforge and it comes in a tar.bz2 archive with no .configure and no instructions regarding install. However, the archive contains a Makefile.
Looking at the Makefile (and what little documentation on sourcefourge) looks like the only dependencies are qt4, which are installed on my system at /usr/share/qt4, as the Makefile seems to require.
What am I supposed to do in order to install this package ?
Link to the sourceforge page:
https://sourceforge.net/projects/targui/
UPDATE
The Makefile has this comment:
#
Makefile for building: targui
Generated by qmake (2.01a) (Qt 4.3.2) on: Fr Dez 28 12:32:13 2007
Project: targui.pro
Template: app
Command: /usr/bin/qmake -unix -o Makefile targui.pro
#
So, from within the directory containing the targui folder I tried:
/usr/bin/qmake -unix -o Makefile targui.pro
but terminal says:
qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file or directory
UPDATE 2
Built according to NOorbert instructions. It segfaults
Fixed mainwindow.cpp so now it looks like:
void MainWindow::TabChanged(int i)
if (newAct) newAct->setEnabled(i > 0);
if (openAct) openAct->setEnabled(i > 0);
if (saveAct) saveAct->setEnabled(i > 0);
if (saveAsAct) saveAsAct->setEnabled(i > 0);
and changed the tar references to /bin in the same file
.targui still segfaults
software-installation compiling make
I downloaded targui from sourceforge and it comes in a tar.bz2 archive with no .configure and no instructions regarding install. However, the archive contains a Makefile.
Looking at the Makefile (and what little documentation on sourcefourge) looks like the only dependencies are qt4, which are installed on my system at /usr/share/qt4, as the Makefile seems to require.
What am I supposed to do in order to install this package ?
Link to the sourceforge page:
https://sourceforge.net/projects/targui/
UPDATE
The Makefile has this comment:
#
Makefile for building: targui
Generated by qmake (2.01a) (Qt 4.3.2) on: Fr Dez 28 12:32:13 2007
Project: targui.pro
Template: app
Command: /usr/bin/qmake -unix -o Makefile targui.pro
#
So, from within the directory containing the targui folder I tried:
/usr/bin/qmake -unix -o Makefile targui.pro
but terminal says:
qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file or directory
UPDATE 2
Built according to NOorbert instructions. It segfaults
Fixed mainwindow.cpp so now it looks like:
void MainWindow::TabChanged(int i)
if (newAct) newAct->setEnabled(i > 0);
if (openAct) openAct->setEnabled(i > 0);
if (saveAct) saveAct->setEnabled(i > 0);
if (saveAsAct) saveAsAct->setEnabled(i > 0);
and changed the tar references to /bin in the same file
.targui still segfaults
software-installation compiling make
edited Aug 20 at 13:20
asked Aug 20 at 10:31
Gumbo
215
215
I got the binary to build but it segfaults immediately on execution; do you still want to know the steps I followed?
â dsstorefile1
Aug 20 at 10:49
Yes please, maybe I got better luck...
â Gumbo
Aug 20 at 11:03
I got around the segfault, see below.
â dsstorefile1
Aug 20 at 11:45
add a comment |Â
I got the binary to build but it segfaults immediately on execution; do you still want to know the steps I followed?
â dsstorefile1
Aug 20 at 10:49
Yes please, maybe I got better luck...
â Gumbo
Aug 20 at 11:03
I got around the segfault, see below.
â dsstorefile1
Aug 20 at 11:45
I got the binary to build but it segfaults immediately on execution; do you still want to know the steps I followed?
â dsstorefile1
Aug 20 at 10:49
I got the binary to build but it segfaults immediately on execution; do you still want to know the steps I followed?
â dsstorefile1
Aug 20 at 10:49
Yes please, maybe I got better luck...
â Gumbo
Aug 20 at 11:03
Yes please, maybe I got better luck...
â Gumbo
Aug 20 at 11:03
I got around the segfault, see below.
â dsstorefile1
Aug 20 at 11:45
I got around the segfault, see below.
â dsstorefile1
Aug 20 at 11:45
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
2
down vote
Build targui
as in N0rbert's answer, then read below for getting the binary to run.
The
targui
segfault on startup is due toMainWindow::TabChanged
frommainwindow.cpp
dereferencing invalid pointers, and adding checks here allows the program to start. For instance, changenewAct->setEnabled(i > 0);
toif (newAct) newAct->setEnabled(i > 0);
, and do the same for the other three pointers.mainwindow.cpp
contains hardcoded strings like/usr/bin/tar
that might not point to extant binaries. For instance, Ubuntu'star
is in/bin
, so fix them accordingly.
Built targui according to NOrbert answer. It segfaults on startup. Followed dssstorefile indications so now >void MainWindow::TabChanged(int i) >if (newAct) newAct->setEnabled(i > 0); >if (openAct) openAct->setEnabled(i > 0); >if (saveAct) saveAct->setEnabled(i > 0); >if (saveAsAct) saveAsAct->setEnabled(i > 0); >
â Gumbo
Aug 20 at 13:08
See update 2 above for proper code
â Gumbo
Aug 20 at 13:22
@ NOrbert, as far as what I want to do with it, i've been looking for a TAR GUI to back up to tape, which is beyond the capabilities of file roller and such, if I'm not wrong.
â Gumbo
Aug 20 at 13:24
add a comment |Â
up vote
2
down vote
You need to install qmake for Qt4 and development packages for it:
sudo apt-get install qt4-qmake libqt4-dev
then run make
:
cd ~/Downloads
tar -xf targui-0.3_beta.tar.bz2
cd targui
make
and then run the application
./targui
but it segfaults on my Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS:
Segmentation fault (core dumped)
Then you should decide - what do you want to achieve by compiling application from 2008 year ten years after.
If you simply need graphical archival tool - you can use File Roller (on GNOME), Engrampa (on MATE) and so on.
add a comment |Â
up vote
0
down vote
In order to get targui not to segfault, the changes to mainwindow.cpp according to dsstorefile1 answer must be done BEFORE and NOT AFTER compiling, according to NOrbert answer.
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Build targui
as in N0rbert's answer, then read below for getting the binary to run.
The
targui
segfault on startup is due toMainWindow::TabChanged
frommainwindow.cpp
dereferencing invalid pointers, and adding checks here allows the program to start. For instance, changenewAct->setEnabled(i > 0);
toif (newAct) newAct->setEnabled(i > 0);
, and do the same for the other three pointers.mainwindow.cpp
contains hardcoded strings like/usr/bin/tar
that might not point to extant binaries. For instance, Ubuntu'star
is in/bin
, so fix them accordingly.
Built targui according to NOrbert answer. It segfaults on startup. Followed dssstorefile indications so now >void MainWindow::TabChanged(int i) >if (newAct) newAct->setEnabled(i > 0); >if (openAct) openAct->setEnabled(i > 0); >if (saveAct) saveAct->setEnabled(i > 0); >if (saveAsAct) saveAsAct->setEnabled(i > 0); >
â Gumbo
Aug 20 at 13:08
See update 2 above for proper code
â Gumbo
Aug 20 at 13:22
@ NOrbert, as far as what I want to do with it, i've been looking for a TAR GUI to back up to tape, which is beyond the capabilities of file roller and such, if I'm not wrong.
â Gumbo
Aug 20 at 13:24
add a comment |Â
up vote
2
down vote
Build targui
as in N0rbert's answer, then read below for getting the binary to run.
The
targui
segfault on startup is due toMainWindow::TabChanged
frommainwindow.cpp
dereferencing invalid pointers, and adding checks here allows the program to start. For instance, changenewAct->setEnabled(i > 0);
toif (newAct) newAct->setEnabled(i > 0);
, and do the same for the other three pointers.mainwindow.cpp
contains hardcoded strings like/usr/bin/tar
that might not point to extant binaries. For instance, Ubuntu'star
is in/bin
, so fix them accordingly.
Built targui according to NOrbert answer. It segfaults on startup. Followed dssstorefile indications so now >void MainWindow::TabChanged(int i) >if (newAct) newAct->setEnabled(i > 0); >if (openAct) openAct->setEnabled(i > 0); >if (saveAct) saveAct->setEnabled(i > 0); >if (saveAsAct) saveAsAct->setEnabled(i > 0); >
â Gumbo
Aug 20 at 13:08
See update 2 above for proper code
â Gumbo
Aug 20 at 13:22
@ NOrbert, as far as what I want to do with it, i've been looking for a TAR GUI to back up to tape, which is beyond the capabilities of file roller and such, if I'm not wrong.
â Gumbo
Aug 20 at 13:24
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Build targui
as in N0rbert's answer, then read below for getting the binary to run.
The
targui
segfault on startup is due toMainWindow::TabChanged
frommainwindow.cpp
dereferencing invalid pointers, and adding checks here allows the program to start. For instance, changenewAct->setEnabled(i > 0);
toif (newAct) newAct->setEnabled(i > 0);
, and do the same for the other three pointers.mainwindow.cpp
contains hardcoded strings like/usr/bin/tar
that might not point to extant binaries. For instance, Ubuntu'star
is in/bin
, so fix them accordingly.
Build targui
as in N0rbert's answer, then read below for getting the binary to run.
The
targui
segfault on startup is due toMainWindow::TabChanged
frommainwindow.cpp
dereferencing invalid pointers, and adding checks here allows the program to start. For instance, changenewAct->setEnabled(i > 0);
toif (newAct) newAct->setEnabled(i > 0);
, and do the same for the other three pointers.mainwindow.cpp
contains hardcoded strings like/usr/bin/tar
that might not point to extant binaries. For instance, Ubuntu'star
is in/bin
, so fix them accordingly.
answered Aug 20 at 11:45
dsstorefile1
1,303111
1,303111
Built targui according to NOrbert answer. It segfaults on startup. Followed dssstorefile indications so now >void MainWindow::TabChanged(int i) >if (newAct) newAct->setEnabled(i > 0); >if (openAct) openAct->setEnabled(i > 0); >if (saveAct) saveAct->setEnabled(i > 0); >if (saveAsAct) saveAsAct->setEnabled(i > 0); >
â Gumbo
Aug 20 at 13:08
See update 2 above for proper code
â Gumbo
Aug 20 at 13:22
@ NOrbert, as far as what I want to do with it, i've been looking for a TAR GUI to back up to tape, which is beyond the capabilities of file roller and such, if I'm not wrong.
â Gumbo
Aug 20 at 13:24
add a comment |Â
Built targui according to NOrbert answer. It segfaults on startup. Followed dssstorefile indications so now >void MainWindow::TabChanged(int i) >if (newAct) newAct->setEnabled(i > 0); >if (openAct) openAct->setEnabled(i > 0); >if (saveAct) saveAct->setEnabled(i > 0); >if (saveAsAct) saveAsAct->setEnabled(i > 0); >
â Gumbo
Aug 20 at 13:08
See update 2 above for proper code
â Gumbo
Aug 20 at 13:22
@ NOrbert, as far as what I want to do with it, i've been looking for a TAR GUI to back up to tape, which is beyond the capabilities of file roller and such, if I'm not wrong.
â Gumbo
Aug 20 at 13:24
Built targui according to NOrbert answer. It segfaults on startup. Followed dssstorefile indications so now >void MainWindow::TabChanged(int i) >if (newAct) newAct->setEnabled(i > 0); >if (openAct) openAct->setEnabled(i > 0); >if (saveAct) saveAct->setEnabled(i > 0); >if (saveAsAct) saveAsAct->setEnabled(i > 0); >
â Gumbo
Aug 20 at 13:08
Built targui according to NOrbert answer. It segfaults on startup. Followed dssstorefile indications so now >void MainWindow::TabChanged(int i) >if (newAct) newAct->setEnabled(i > 0); >if (openAct) openAct->setEnabled(i > 0); >if (saveAct) saveAct->setEnabled(i > 0); >if (saveAsAct) saveAsAct->setEnabled(i > 0); >
â Gumbo
Aug 20 at 13:08
See update 2 above for proper code
â Gumbo
Aug 20 at 13:22
See update 2 above for proper code
â Gumbo
Aug 20 at 13:22
@ NOrbert, as far as what I want to do with it, i've been looking for a TAR GUI to back up to tape, which is beyond the capabilities of file roller and such, if I'm not wrong.
â Gumbo
Aug 20 at 13:24
@ NOrbert, as far as what I want to do with it, i've been looking for a TAR GUI to back up to tape, which is beyond the capabilities of file roller and such, if I'm not wrong.
â Gumbo
Aug 20 at 13:24
add a comment |Â
up vote
2
down vote
You need to install qmake for Qt4 and development packages for it:
sudo apt-get install qt4-qmake libqt4-dev
then run make
:
cd ~/Downloads
tar -xf targui-0.3_beta.tar.bz2
cd targui
make
and then run the application
./targui
but it segfaults on my Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS:
Segmentation fault (core dumped)
Then you should decide - what do you want to achieve by compiling application from 2008 year ten years after.
If you simply need graphical archival tool - you can use File Roller (on GNOME), Engrampa (on MATE) and so on.
add a comment |Â
up vote
2
down vote
You need to install qmake for Qt4 and development packages for it:
sudo apt-get install qt4-qmake libqt4-dev
then run make
:
cd ~/Downloads
tar -xf targui-0.3_beta.tar.bz2
cd targui
make
and then run the application
./targui
but it segfaults on my Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS:
Segmentation fault (core dumped)
Then you should decide - what do you want to achieve by compiling application from 2008 year ten years after.
If you simply need graphical archival tool - you can use File Roller (on GNOME), Engrampa (on MATE) and so on.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
You need to install qmake for Qt4 and development packages for it:
sudo apt-get install qt4-qmake libqt4-dev
then run make
:
cd ~/Downloads
tar -xf targui-0.3_beta.tar.bz2
cd targui
make
and then run the application
./targui
but it segfaults on my Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS:
Segmentation fault (core dumped)
Then you should decide - what do you want to achieve by compiling application from 2008 year ten years after.
If you simply need graphical archival tool - you can use File Roller (on GNOME), Engrampa (on MATE) and so on.
You need to install qmake for Qt4 and development packages for it:
sudo apt-get install qt4-qmake libqt4-dev
then run make
:
cd ~/Downloads
tar -xf targui-0.3_beta.tar.bz2
cd targui
make
and then run the application
./targui
but it segfaults on my Ubuntu 14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS:
Segmentation fault (core dumped)
Then you should decide - what do you want to achieve by compiling application from 2008 year ten years after.
If you simply need graphical archival tool - you can use File Roller (on GNOME), Engrampa (on MATE) and so on.
edited Aug 20 at 11:46
answered Aug 20 at 11:38
N0rbert
15k33069
15k33069
add a comment |Â
add a comment |Â
up vote
0
down vote
In order to get targui not to segfault, the changes to mainwindow.cpp according to dsstorefile1 answer must be done BEFORE and NOT AFTER compiling, according to NOrbert answer.
add a comment |Â
up vote
0
down vote
In order to get targui not to segfault, the changes to mainwindow.cpp according to dsstorefile1 answer must be done BEFORE and NOT AFTER compiling, according to NOrbert answer.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
In order to get targui not to segfault, the changes to mainwindow.cpp according to dsstorefile1 answer must be done BEFORE and NOT AFTER compiling, according to NOrbert answer.
In order to get targui not to segfault, the changes to mainwindow.cpp according to dsstorefile1 answer must be done BEFORE and NOT AFTER compiling, according to NOrbert answer.
answered Aug 21 at 1:45
Gumbo
215
215
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1067105%2finstalling-tar-bz2-with-no-configure-but-with-makefile-in-it%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I got the binary to build but it segfaults immediately on execution; do you still want to know the steps I followed?
â dsstorefile1
Aug 20 at 10:49
Yes please, maybe I got better luck...
â Gumbo
Aug 20 at 11:03
I got around the segfault, see below.
â dsstorefile1
Aug 20 at 11:45