Maurilio:
>while the last 3.3.5 in the path depends on GCC version and so it
>changes from release to release.
>So we have to parse LIBRARY_PATH to add -L options to ld command line,
>but it is not enough since we need an object, dll0.o, which is inside
>E:/SVILUPPO/GCC/V3.3.5/USR/lib/dll0.o
>which could be inferred from LIBRARY_PATH, but I don't know whether
the >new versions of GCC have it in the same position.
>This is something that has to be hard-coded inside gcc when used as
>dl.exe front end which should be extracted from it in some way.
Newer os2gcc are installed usually in \usr\(compiler), but os2gcc335 is
*mandatory* to be installed too, as newer rely in some gcc335 tools
In my machine gcc335 is in \usr\
gcc442 in \usr\local442 and dll0.o exist only in \usr\lib
So path, references for both compilers are included, newer first
>I'd say yes, the OMF version has an .obj extension.
No. Due facts Viktor knows well, .o was impossed to both, a.out and OMF
.obj for OMF was excluded
>Who/what is setting LIBRARY_PATH? Should it be set by user,
>or is it set by some of the GCC tools in GCC toolchain?
This setting can be changed dinamically to fit requirements of many
systems, not only os2gcc
>Sorry if I missed it, but can you paste here a living
>example for what value it's actually set to?
>I'd also like to include it in INSTALL, since it's
>apparently missing.
>Ok, but is there a way, inside .mk files to split an env-var using
some >char as delimiter? if yes, than we can create the command line for
ld >which has this sequence of paths as a variable part, while the rest
>should be pretty fixed.
I do tests with many os2gcc compilers, so forcing values for
ld.exe/emxomfld.exe should be practical
For example, for os2gcc442, which show gcc442,gcc335 references:
-------------------------
PATH_EMXPGCC=E:\usr
CCENV=EMX
BUILD_ENV=EMX
BUILD_PLATFORM=OS2
DPATH=E:\usr\local442\lib;E:\usr\lib;E:\MPTN; ...
PATH=E:\usr\local442\libexec\gcc\i386-pc-os2-emx\4.4.2;E:\usr\local442\bin;E:\usr\bin;
...
C_INCLUDE_PATH=E:/usr/local442/lib/gcc/i386-pc-os2-emx/4.4.2/include;E:/usr/local442/include;E:/usr/include;
CPLUS_INCLUDE_PATH=E:/usr/local442/include/c++/4.4.2;E:/usr/local442/include/c++/4.4.2/i386-pc-os2-emx;E:/usr/local442/include/c++/4.4.2/backward;E:/usr/local442/include;E:/usr/include;
LIBRARY_PATH=E:/usr/local442/lib/gcc/i386-pc-os2-emx/4.4.2;E:/usr/local442/lib;E:/usr/lib;
INFOPATH=E:/usr/local442/info;E:/usr/info;
PROTODIR=E:/usr/include/c++/gen
BEGINLIBPATH=E:\usr\local442\lib;E:\usr\lib;
-------------------------
>No, the harbour build process should not set nor change LIBRARY_PATH,
>this has to be set and be correct _before_ installing harbour.
Fully agree. See above
David Macias
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
