>>> -LE:/Sviluppo/gcc/v3.3.5/usr/lib/gcc-lib/i386-pc-os2-emx/3.3.5 >>> >>> E:/SVILUPPO/GCC/V3.3.5/ is where I decided to put GCC on my system, while >>> the >>> last 3.3.5 in the path depends on GCC version and so it changes from release >>> to release. >> >> Is '/gcc/3.3.5/' a mandatory element of the base dir, or >> local user preference? I mean, may I simple install it >> to 'E:/os2stuff/gcc/' instead of 'E:/Sviluppo/gcc/v3.3.5/'? >> > Sure.
This means we can't use base path to get version information needed to form paths for ld.exe. To me it's unclear how to make this automatic or elegant. I think the bug should be reported to GCC maintainers, to get it fixed ASAP. >>> 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. >> >> That's a question. Plus whether it's in the same place for >> gccomf vs plain gcc. >> > I'd say yes, the OMF version has an .obj extension. > > dir \*dll0.* /s > > The volume label in drive E is Dati. > The Volume Serial Number is 812E:D5C2. > > Directory of E:\Sviluppo\gcc\v3.3.5\usr\lib > > 11/06/07 22:52 1.955 0 a--- dll0.o > 11/06/07 22:52 2.797 0 a--- dll0.obj > 2 file(s) 4.752 bytes used Okay. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
