OS/2, eCS & ArcaOS - Technical > Programming
Porting a UNIX application with autotools - ilink.exe error
(1/1)
snw:
Hello all,
I am porting my UNIX application (which uses autoconf, automake, and libtool) to ArcaOS.
Things seem to go splendidly until the link phase, when it complains "ilink.exe: No such file or directory".
I have gcc-wlink and gcc-wrc installed, so I'm unsure as to why it's trying to use ilink.exe. I build
in a bash environment.
Any pointers?
Thanks in advance!
snw:
A note: I've attempted `./configure LD=/usr/bin/wl.exe` as well as `export LD=/usr/bin/wl.exe` prior to configuring/building, to no effect.
Dave Yeo:
You need to set some environment parameters. Run emxomfld with no parameters to see,
--- Code: ---Environment variables:
EMXOMFLD_TYPE:
The type of linker we're using. Values: WLINK, VAC365, VAC308, LINK386.
WLINK wlink.exe from Open Watcom v1.5 or later.
VAC365 ilink.exe from IBM C and C++ Compilers for OS/2 v3.6 or later.
VAC308 ilink.exe from Visual Age for C++ v3.08.
LINK386 link386 form OS/2 install or DDK.
EMXOMFLD_LINKER:
Name of the linker to use and optionally extra parameters. Spaces in the
linker name or path is not supported. Quotes are not supported either.
The default values for these two variables are VAC365 and ilink.exe.
EMXOMFLD_RC_TYPE:
The type of resource compiler we're using. Values: RC,WRC.
RC rc.exe as shipped with OS/2 or found in the Toolkit
WRC wrc.exe from Open Watcom v1.6 or later.
EMXOMFLD_RC:
Name of the resource compiler to use and optionally extra parameters.
Spaces or quotes in the name or path are not supported.
The default values for these two variables are RC and rc.exe.
--- End code ---
So, I use something like,
--- Code: ---set EMXOMFLD_TYPE=WLINK
set EMXOMFLD_LINKER=wl.exe
--- End code ---
Might need the full path to wl.exe
snw:
This worked splendidly! Thank you much.
Navigation
[0] Message Index
Go to full version