Difference between revisions of "64bit Linux issues"
From Noah.org
Jump to navigationJump to searchLine 2: | Line 2: | ||
Almost all source packages use the "./configure && make && make install" idiom. | Almost all source packages use the "./configure && make && make install" idiom. | ||
− | This is well and fine, but most of the "configure" scripts were | + | This is well and fine, but most of the "configure" scripts were generated with |
− | autoconf on 32-bit machines. You may see this error when you try to build a package from source | + | `autoconf` on 32-bit machines. You may see this error when you try to build a package from source |
on 64-bit Linux: | on 64-bit Linux: | ||
/usr/lib/libpopt.so: could not read symbols: File in wrong format | /usr/lib/libpopt.so: could not read symbols: File in wrong format |
Revision as of 15:00, 15 August 2007
Almost all source packages use the "./configure && make && make install" idiom.
This is well and fine, but most of the "configure" scripts were generated with
`autoconf` on 32-bit machines. You may see this error when you try to build a package from source
on 64-bit Linux:
/usr/lib/libpopt.so: could not read symbols: File in wrong format
Simply regenerate the "configure" script:
autoreconf -f -i
Then try the ancient incantation again:
./configure && make && make install