You are not logged in.

#1 2013-03-26 07:09:31

vortex59
Member
From: Timisoara, Romania
Registered: 2011-01-15
Posts: 10

[SOLVED] lib32 problem on x86_64

I have the following problem on Arch x86_64 (2013.03.01): a 32 bit console chemistry program (firefly, former pcgamess, build in 2009) does not run. It starts but no output and "run forever" (CTRL-Z to stop). No message of missing library. I have installed lib32-glibc, lib32-gcc-libs, lib32-ncurses, lib32-libstdc++5 , etc. Do I missed something? Other 32 bit programs works fine. One year ago, on an older Arch computer it worked.

The computer is a Fujitsu-Siemens, Quad Core, 2.41 GHz, 4 GB RAM, HDD 500 GB, GFORCE 7600 video.

Last edited by vortex59 (2014-03-13 22:14:03)


"A scientist is someone whose curiosity survives education's assaults on it"
Sir Herman Bondi

Offline

#2 2013-03-26 11:46:20

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: [SOLVED] lib32 problem on x86_64

Does it give some error messages if you start it from terminal ?

also on the downloadpage for firefly 7.1G , they mention there's a patch to allow firefly to work with recent kernels .
http://classic.chem.msu.su/gran/gamess/patchff71g.zip

Is that patch installed ?

Edit :
are you using a static or dynamically linked version ?

Last edited by Lone_Wolf (2013-03-26 11:47:42)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2013-03-26 12:03:18

vortex59
Member
From: Timisoara, Romania
Registered: 2011-01-15
Posts: 10

Re: [SOLVED] lib32 problem on x86_64

1 - No messages.
2 - As I know, the patch applies only for kernel issues due to the jump to 3.0 versions. Any way I will give a try also with the patch.
3 - Fully static.

I tested on a Mint-Debian computer (x86_64) an it works without the patch. For Mint-Debian there is a full package of 32 libs (ia32-libs) which is installed on request. It is strange on Arch with no message on console requesting some libraries...


"A scientist is someone whose curiosity survives education's assaults on it"
Sir Herman Bondi

Offline

#4 2013-03-26 12:18:09

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: [SOLVED] lib32 problem on x86_64

Yeah, afaik there's no arch equivalent for ia32-libs .
And with proprietary software where you need a key to extract the binaries, it's hard to figure out the real dependencies.

You might have to fall back to using ldd to figure out which libraries it's missing.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#5 2013-03-26 12:20:58

vortex59
Member
From: Timisoara, Romania
Registered: 2011-01-15
Posts: 10

Re: [SOLVED] lib32 problem on x86_64

Thanks! I will work around.
==================
That's what I received from ldd ./firefly

[mihai@ChemArch firefly]$ ldd ./firefly
    linux-gate.so.1 (0xf77a5000)
    libm.so.6 => /usr/lib32/libm.so.6 (0xf7745000)
    libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf772a000)
    libc.so.6 => /usr/lib32/libc.so.6 (0xf7579000)
    /lib/ld-linux.so.2 (0xf77a6000)

and that is what I received from another 32 bit console program which works

[mihai@ChemArch gm01]$ ldd gm01
    linux-gate.so.1 (0xf779f000)
    libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf7767000)
    libm.so.6 => /usr/lib32/libm.so.6 (0xf7724000)
    libc.so.6 => /usr/lib32/libc.so.6 (0xf7573000)
    librt.so.1 => /usr/lib32/librt.so.1 (0xf756a000)
    /lib/ld-linux.so.2 (0xf77a0000)

Any more ideas?

Last edited by vortex59 (2013-03-28 09:30:09)


"A scientist is someone whose curiosity survives education's assaults on it"
Sir Herman Bondi

Offline

#6 2013-03-28 09:59:33

vortex59
Member
From: Timisoara, Romania
Registered: 2011-01-15
Posts: 10

Re: [SOLVED] lib32 problem on x86_64

Something else on the same subject: with "ld firefly" I've got:

[mihai@ChemArch firefly]$ ld firefly
  ld: i386 architecture of input file `firefly' is incompatible with i386:x86-64 output
  ld: error in firefly(.eh_frame); no .eh_frame_hdr table will be created.
  ld: warning: cannot find entry symbol _start; defaulting to 0000000000404ad0

Again: any ideas?

Thanks


"A scientist is someone whose curiosity survives education's assaults on it"
Sir Herman Bondi

Offline

#7 2013-03-28 10:18:31

progandy
Member
Registered: 2012-05-17
Posts: 5,190

Re: [SOLVED] lib32 problem on x86_64

ld is the linker, not the loader. Maybe you wanted to try this:
/usr/lib32/ld-linux.so.2 --verify firefly
/usr/lib32/ld-linux.so.2 --list firefly

Edit: The firefly homepage has different versions, maybe you want to try a different one (choose other optimization methods, ...).

Last edited by progandy (2013-03-28 10:26:17)


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

#8 2013-04-24 10:43:55

vortex59
Member
From: Timisoara, Romania
Registered: 2011-01-15
Posts: 10

Re: [SOLVED] lib32 problem on x86_64

Back again! after enough "long" time (2-3 minutes) the comand ./firefly gave on terminal the following error:

[mihai@mmArch firefly]$ ./firefly
p0_28024:  p4_error: Could not gethostbyname for host mmArch; may be invalid name
: 61

Any ideas?


"A scientist is someone whose curiosity survives education's assaults on it"
Sir Herman Bondi

Offline

#9 2013-04-25 08:01:42

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: [SOLVED] lib32 problem on x86_64

Could be  a problem with the network configuration on your system, check http://blog.tempusdictum.com/index.php/ … e-for-host


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#10 2013-04-25 17:58:16

vortex59
Member
From: Timisoara, Romania
Registered: 2011-01-15
Posts: 10

Re: [SOLVED] lib32 problem on x86_64

Build that program. After runing it I got:

user_host = mmArch
gethostbyname(gethostname()) = mmArch
hostname(/*hardcoded*/ "hostname") failed

Any significance?


"A scientist is someone whose curiosity survives education's assaults on it"
Sir Herman Bondi

Offline

#11 2013-04-26 09:30:03

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,911

Re: [SOLVED] lib32 problem on x86_64

Yes, that strongly suggests something in /etc/hostname file is not correct.

Check it thoroughly in a good editor for extra stuff like additional spaces or weird characters.
If you don't see anythin wrong with it, redirect the output of the program to a file and check that file carefully.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#12 2014-03-13 22:12:20

vortex59
Member
From: Timisoara, Romania
Registered: 2011-01-15
Posts: 10

Re: [SOLVED] lib32 problem on x86_64

After almost one year I found the solution (well, I did not work only on this one smile  ). Running the program mentioned above gave the same results on a computer with Linux Mint 13 Mate64 but the program firefly worked with no problems. I saw that the hostname was also in file hosts. So, for me the solution was to put the hostname in "hosts" file (/etc/hosts) :

#<ip-address>	<hostname.domain.org>	<hostname>
127.0.0.1       localhost.localdomain	ChemArch

where ChemArch is now the hostname and everything works for firefly program.


"A scientist is someone whose curiosity survives education's assaults on it"
Sir Herman Bondi

Offline

#13 2014-03-13 23:25:42

progandy
Member
Registered: 2012-05-17
Posts: 5,190

Re: [SOLVED] lib32 problem on x86_64

vortex59 wrote:

After almost one year I found the solution (well, I did not work only on this one smile  ). Running the program mentioned above gave the same results on a computer with Linux Mint 13 Mate64 but the program firefly worked with no problems. I saw that the hostname was also in file hosts. So, for me the solution was to put the hostname in "hosts" file (/etc/hosts) :

#<ip-address>	<hostname.domain.org>	<hostname>
127.0.0.1       localhost.localdomain	ChemArch

where ChemArch is now the hostname and everything works for firefly program.

Good. Although the nss-myhostname(8) module should take care of that automatically in up-to-date arch installations.


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

Board footer

Powered by FluxBB