I assume you are using gcc to compile. With gcc, the flag "-m32" will compile it 32-bit on a 64-bit platform.
From the gcc man page:
-m32 -m64 Generate code for a 32-bit or 64-bit environment. The 32-bit environment sets int, long and pointer to 32 bits. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits. A plugin I am working on shows the following from file: [EMAIL PROTECTED] ardbcsql]# file ardbcsql.so ardbcsql.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped I The file above, showing not stripped, does load and run as expected. Stripped just means that the debugging symbols were removed from the file. If you want to remove the symbols, you can use the strip command to do that, though it shouldn't make a difference. Do an ldd on the 32-bit version and make sure it is referencing the 32-bit libs. Axton Grams On 7/20/07, Mark Milke <[EMAIL PROTECTED]> wrote:
now, there is funny thing: all ardbc plug-ins that work are 32-bit! [EMAIL PROTECTED] bin]$ file ardbcconf.so ardbcconf.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped SO now, I have a 32-bit version one guy compiled for me on 32-bit LINUX HERE: [EMAIL PROTECTED] bin]$ file ardbccsv.so ardbccsv.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped The only difference is stripped vs. not stripped. Do you think this is a problem? Guess what! It works!!!! Thanks _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
