OS/2, eCS & ArcaOS - Technical > Programming

How to specify wlink as linker for gcc?

<< < (2/2)

Dave Yeo:
Most everything needed can be installed with yum/rpm and has the advantage of being a standard environment. One problem with GCC and home spun environments is sometimes no one else can repeat what you did.

R.M. Klippstein:
Thanks Guys -- Looks Like YUM, for sure, is the way to go, I didn't realize GCC was available on YUM. I've got by the linker problem thanks to you, and now am in the build phase --YUK! Could you possibly straighten me out on another thing I don't completely understand? I'm familiar with SYMLINKS in Linux but not so smart when it comes to SYMLINKS in OS/2 -- I guess they are similar to shadows. My problem is I need to create a couple of Symlinks in the <libc trunk>. 
kmk_ln -s <libc trunk> /libc/include/os2d
kmk_ln -s <libc trunk>/kLdr src/VBox/Run

I don't understand, where & what,  is meant  by <klibc trunk>!  Would these need to be in the enviorment,  GCC (gccenv, or SET statement in config.sys?). I don't understand what to specify as <klibc trunk!>?
Thanks for the help & sorry to keep bothering you.   klipp

Dave Yeo:
Usually symlinks are implemented at the file system level which on OS/2 limits you to TVFS. klibc does it differently, supporting symlinks at the libc level so created symlinks only work with applications linked to libc. You can build coreutils or easier install with yum and get a working ln.exe, but only for symlinks and only in the libc environment.
The usual way of handling symlinks is to just copy, LN_S=cp -f.
Libc trunk is the main libc directory if you check out libc07 with svn I believe,

--- Code: ---svn co http://svn.netlabs.org/repos/libc/trunk
--- End code ---
See http://trac.netlabs.org/libc
ps symlinks and permissions are kept in EAs and if using HPFS are actually compatible with Linux so a symlink created under OS/2 on HPFS will work on Linux and vice versa. 

Navigation

[0] Message Index

[*] Previous page

Go to full version