OpendTect 6.2.0 bad installation in Ubuntu 18.04 LTS x64
Some days ago I were trying to install OpendTect in Ubuntu, I have the .sh OpendTect installer for linux.
I did run:
chmod a+x OpendTect_Installer_lux32.sh
./OpendTect_Installer_lux64.sh
And the installer is similar to windows, when the "windows look like install finish" and it says everything's fine in the terminal says core dumped
and i can't run start_dtect
because it says the same error core dumped
.
software-installation 18.04
add a comment |
Some days ago I were trying to install OpendTect in Ubuntu, I have the .sh OpendTect installer for linux.
I did run:
chmod a+x OpendTect_Installer_lux32.sh
./OpendTect_Installer_lux64.sh
And the installer is similar to windows, when the "windows look like install finish" and it says everything's fine in the terminal says core dumped
and i can't run start_dtect
because it says the same error core dumped
.
software-installation 18.04
add a comment |
Some days ago I were trying to install OpendTect in Ubuntu, I have the .sh OpendTect installer for linux.
I did run:
chmod a+x OpendTect_Installer_lux32.sh
./OpendTect_Installer_lux64.sh
And the installer is similar to windows, when the "windows look like install finish" and it says everything's fine in the terminal says core dumped
and i can't run start_dtect
because it says the same error core dumped
.
software-installation 18.04
Some days ago I were trying to install OpendTect in Ubuntu, I have the .sh OpendTect installer for linux.
I did run:
chmod a+x OpendTect_Installer_lux32.sh
./OpendTect_Installer_lux64.sh
And the installer is similar to windows, when the "windows look like install finish" and it says everything's fine in the terminal says core dumped
and i can't run start_dtect
because it says the same error core dumped
.
software-installation 18.04
software-installation 18.04
edited Jun 12 '18 at 14:43
N0rbert
23.3k649111
23.3k649111
asked Jun 12 '18 at 14:17
Rosendo OcañaRosendo Ocaña
61
61
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I have installed it with the actions below:
sudo apt-get install csh
cd ~/Downloads
wget http://download.opendtect.org/relman/OpendTect_Installer_lux64.sh
sh OpendTect_Installer_lux64.sh
It was installed to ~/OpendTect.
If I start it with ~/OpendTect/6.2.0/start_dtect I get the sameSegmentation fault (core dumped)
.
But I can launch it by command (specifying library directory manually)
LD_LIBRARY_PATH=/home/$USER/OpendTect/6.2.0/bin/lux64/Release
/home/$USER/OpendTect/6.2.0/bin/lux64/Release/od_main
Note: I have never used this software, just installed to help you.
add a comment |
@N0rbert gave usefull informations here.
OpendTect uses csh scripts to set up the necessary environment and these fail with a segfault. After digging a bit, I found that the segfault is caused by
eval `"${DTECT_APPL}/bin/mksethdir"`
Replacing this line in two scripts with setenv HDIR lux64; setenv binsubdir lux64
fix the issue.
In my case I have a lux64
folder in OpendTect/6.4.0/bin/
. If it's not the case for you, change lux64
by whatever you have.
Here is the quick fix with sed :
cd ~/OpendTect/6.4.0/bin # or wherever your opendtect folder is
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' init_dtect
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' od_exec
If anyone knows why eval
is failing here, let us know.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045930%2fopendtect-6-2-0-bad-installation-in-ubuntu-18-04-lts-x64%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have installed it with the actions below:
sudo apt-get install csh
cd ~/Downloads
wget http://download.opendtect.org/relman/OpendTect_Installer_lux64.sh
sh OpendTect_Installer_lux64.sh
It was installed to ~/OpendTect.
If I start it with ~/OpendTect/6.2.0/start_dtect I get the sameSegmentation fault (core dumped)
.
But I can launch it by command (specifying library directory manually)
LD_LIBRARY_PATH=/home/$USER/OpendTect/6.2.0/bin/lux64/Release
/home/$USER/OpendTect/6.2.0/bin/lux64/Release/od_main
Note: I have never used this software, just installed to help you.
add a comment |
I have installed it with the actions below:
sudo apt-get install csh
cd ~/Downloads
wget http://download.opendtect.org/relman/OpendTect_Installer_lux64.sh
sh OpendTect_Installer_lux64.sh
It was installed to ~/OpendTect.
If I start it with ~/OpendTect/6.2.0/start_dtect I get the sameSegmentation fault (core dumped)
.
But I can launch it by command (specifying library directory manually)
LD_LIBRARY_PATH=/home/$USER/OpendTect/6.2.0/bin/lux64/Release
/home/$USER/OpendTect/6.2.0/bin/lux64/Release/od_main
Note: I have never used this software, just installed to help you.
add a comment |
I have installed it with the actions below:
sudo apt-get install csh
cd ~/Downloads
wget http://download.opendtect.org/relman/OpendTect_Installer_lux64.sh
sh OpendTect_Installer_lux64.sh
It was installed to ~/OpendTect.
If I start it with ~/OpendTect/6.2.0/start_dtect I get the sameSegmentation fault (core dumped)
.
But I can launch it by command (specifying library directory manually)
LD_LIBRARY_PATH=/home/$USER/OpendTect/6.2.0/bin/lux64/Release
/home/$USER/OpendTect/6.2.0/bin/lux64/Release/od_main
Note: I have never used this software, just installed to help you.
I have installed it with the actions below:
sudo apt-get install csh
cd ~/Downloads
wget http://download.opendtect.org/relman/OpendTect_Installer_lux64.sh
sh OpendTect_Installer_lux64.sh
It was installed to ~/OpendTect.
If I start it with ~/OpendTect/6.2.0/start_dtect I get the sameSegmentation fault (core dumped)
.
But I can launch it by command (specifying library directory manually)
LD_LIBRARY_PATH=/home/$USER/OpendTect/6.2.0/bin/lux64/Release
/home/$USER/OpendTect/6.2.0/bin/lux64/Release/od_main
Note: I have never used this software, just installed to help you.
answered Jun 12 '18 at 14:40
N0rbertN0rbert
23.3k649111
23.3k649111
add a comment |
add a comment |
@N0rbert gave usefull informations here.
OpendTect uses csh scripts to set up the necessary environment and these fail with a segfault. After digging a bit, I found that the segfault is caused by
eval `"${DTECT_APPL}/bin/mksethdir"`
Replacing this line in two scripts with setenv HDIR lux64; setenv binsubdir lux64
fix the issue.
In my case I have a lux64
folder in OpendTect/6.4.0/bin/
. If it's not the case for you, change lux64
by whatever you have.
Here is the quick fix with sed :
cd ~/OpendTect/6.4.0/bin # or wherever your opendtect folder is
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' init_dtect
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' od_exec
If anyone knows why eval
is failing here, let us know.
add a comment |
@N0rbert gave usefull informations here.
OpendTect uses csh scripts to set up the necessary environment and these fail with a segfault. After digging a bit, I found that the segfault is caused by
eval `"${DTECT_APPL}/bin/mksethdir"`
Replacing this line in two scripts with setenv HDIR lux64; setenv binsubdir lux64
fix the issue.
In my case I have a lux64
folder in OpendTect/6.4.0/bin/
. If it's not the case for you, change lux64
by whatever you have.
Here is the quick fix with sed :
cd ~/OpendTect/6.4.0/bin # or wherever your opendtect folder is
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' init_dtect
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' od_exec
If anyone knows why eval
is failing here, let us know.
add a comment |
@N0rbert gave usefull informations here.
OpendTect uses csh scripts to set up the necessary environment and these fail with a segfault. After digging a bit, I found that the segfault is caused by
eval `"${DTECT_APPL}/bin/mksethdir"`
Replacing this line in two scripts with setenv HDIR lux64; setenv binsubdir lux64
fix the issue.
In my case I have a lux64
folder in OpendTect/6.4.0/bin/
. If it's not the case for you, change lux64
by whatever you have.
Here is the quick fix with sed :
cd ~/OpendTect/6.4.0/bin # or wherever your opendtect folder is
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' init_dtect
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' od_exec
If anyone knows why eval
is failing here, let us know.
@N0rbert gave usefull informations here.
OpendTect uses csh scripts to set up the necessary environment and these fail with a segfault. After digging a bit, I found that the segfault is caused by
eval `"${DTECT_APPL}/bin/mksethdir"`
Replacing this line in two scripts with setenv HDIR lux64; setenv binsubdir lux64
fix the issue.
In my case I have a lux64
folder in OpendTect/6.4.0/bin/
. If it's not the case for you, change lux64
by whatever you have.
Here is the quick fix with sed :
cd ~/OpendTect/6.4.0/bin # or wherever your opendtect folder is
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' init_dtect
sed -i 's/eval `"$DTECT_APPL/bin/mksethdir"`/setenv HDIR lux64; setenv binsubdir lux64/g' od_exec
If anyone knows why eval
is failing here, let us know.
answered Jan 31 at 12:16
MaxMax
32115
32115
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045930%2fopendtect-6-2-0-bad-installation-in-ubuntu-18-04-lts-x64%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown