OS/2, eCS & ArcaOS - Technical > Programming
compiling glib-2.36.4 & libidl-0.8.14 -- need help
Dave Yeo:
glibidl_20070521 should only need (environment variables pointing to where you installed it) %GLIB%\gcc\bin;%LIBIDL%\gcc\bin added to the PATH and BEGINLIBPATH.
To compile glib2 from scratch means having the right environment then running [a]sh configure && make
The hard part is having the right environment. Sometimes libtool needs patching as well, at least to produce a DLL.
R.M. Klippstein:
Hi Dave, Unbelievable! I still can't compile (build) using ash. I now have gcc335-(csd4) installed and working in /usr/bin. I also have a /usr/build directory containing the following sources: xpidl,2.2.4 (vbox source),glib-2.36.4, and glib-2.36.4.tar.gz. I did set makeshell=ash. using "ash" as a command doesn't work neither does "[a]sh". The only command sequence that attempts to compile is: gcc -v d:/usr/build/2.2.4. No matter which source I select in the build directory I get the same "malformed input file" error.
Maybe the following screen capture will help you see where I'm screwed up!
The problem has to be right there in front of megcc version 3.3.5 (Bird Build 2011-10-03 04:55 (csd4))
D:/usr/i386-pc-os2-emx/bin/ld.exe -o .exe D:/usr/lib/crt0.o -LD:/usr/lib/gcc-li
b/i386-pc-os2-emx/3.3.5 -LD:/usr/lib/gcc-lib -LD:/usr/lib/gcc-lib/i386-pc-os2-em
x/3.3.5 -LD:/usr/lib -LD:/usr/build/2.2.4 -LD:/USR/lib/gcc-lib/i386-pc-os2-emx/3
.3.5 -LD:/usr/i386-pc-os2-emx/lib -LD:/USR/i386-pc-os2-emx/lib -LD:/usr/lib -LD:
/usr/lib d:/usr/build/2.2.4/ -lc_alias -lc_dll -los2 -lgcc_so_d -lc_alias -lc_dl
l -los2 -lgcc_so_d -lc_alias -lc_dll -los2 -lgcc_so_d -lc_alias -lc_dll -los2 -l
gcc_so_d -lc_alias -lc_dll -los2
D:/usr/i386-pc-os2-emx/bin/ld.exe: malformed input file (not rel or archive) d:/
usr/build/2.2.4/
Apologies for my continued bugging you. klipp
Dave Yeo:
What is generating that insane command? Most of it is automatically found by GCC (and I assume LD) and could be simplified as
--- Code: ---LD -o .exe -LD:/usr/build/2.2.4
or better
GCC -o .exe -LD:/usr/build/2.2.4
--- End code ---
I'm not used to using LD directly but assume -o and -L works the same as GCC. Your executable is missing a prefix and all you're doing is pulling in the stuff that is automatically pulled in and searching for libs in d;/usr/build/2.2.4 which is probably the parent or grandparent of where ever the libs are.
Basdically LD is getting confused by not being fed any objects besides the libc ones that are automatically pulled in.
Navigation
[0] Message Index
[*] Previous page
Go to full version