Member Avatar for biojet

Hi all,

I am a newcomer with linux.
Now,I am trying to install lifescope software but I have problem to do that.
Below that my way to install software:

beowulf@n000 ~]$ tar -xzf LifeScope-2.5.r0-97271_20111110010925.tar.gz
  [beowulf@n000 ~]$ make install
  cat install.sh >install 
  chmod a+x install
  [beowulf@n000 ~]$

Log file of lifescope was attached in this mail.

Could you please show me how to install that software?

LifeScope_011712_0931.log_.zip (660.36 KB)
  • 3 Contributors
  • 4 Replies
  • 314 Views
  • 22 Hours Discussion Span
  • Latest Post Latest Post by rubberman

Dani AI

Generated

The attached archive looks like a packaged installer (the first post shows an install file was created from the archive). Common causes on CentOS 5.7 are: running a binary built for a different CPU bitness, missing runtime libraries, SELinux preventing execution, or running the installer without root privileges. The standard source-build sequence suggested by may not apply if LifeScope ships as a prebuilt installer; as pointed out, the actual install step must run with elevated privileges.

Quick diagnostic checklist (run from inside the extracted tree and adjust paths to match the actual files):

uname -m
file install
ldd path/to/main/executable
grep -i -E 'error|failed|denied' LifeScope*/install.log | tail -n 50

What to look for and remedies:

  • If file shows an ELF 32-bit executable on an x86_64 system, 32-bit runtime libraries are required. Use the package manager to install the 32-bit glibc/libstdc++ runtime packages appropriate for CentOS 5.x (package names commonly include .i386 or .i686).
  • ldd will list any missing shared libraries. Install whatever packages provide those libraries via yum or yum whatprovides.
  • If the log shows “permission denied” despite executable bits being set, test whether SELinux is blocking the installer (check the current mode and, for a short test only, disable enforcement). Re-enable SELinux afterward.
  • The installer must be run with root privileges; prefer elevating only the installer process (sudo) or using a root shell that preserves the current working directory so paths remain valid.

If errors persist, capture the last 50–100 lines of the install log plus the outputs of the file and ldd checks above. Those items are the most useful clues for diagnosing missing libraries or architecture mismatches on CentOS 5.7.

Recommended Answers

All 4 Replies

Member Avatar for khajvah

I dont know about centOS but it seems similar to the way you install on ubuntu.
1.Extract and THEN GO THE DIRECTORY IT IS EXTRACTED( you seem didnt do that (cd LifeScope-2.5.r0-97271_20111110010925))
2.in ubuntu you type: ./configure
3.make
4.make install

Link to UNIX "tar" command
http://www.computerhope.com/unix/utar.htm

Edited by khajvah because: n/a
Member Avatar for rubberman

To install, after building it, you need to run "make install" as root.

Member Avatar for khajvah

To install, after building it, you need to run "make install" as root.

True that, i just didnt know how to do that as root on CentOS. (sudo in ubuntu) :)

Member Avatar for rubberman

From the command line:

cd directory-where-code-is-to-build
su
make install
exit

"su" will ask for the root password. Don't add a dash after 'su' since you want to stay in the build directory to run "make install". As "su" creates a new shell, the "exit" command will return you to the user environment.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.