It's also possible they parse the disk option file, convert it to string and pass it as plain command-line (with 32KB limit) to subprocess.
While disk option files are not _only_ meant to get around cmdline length limitations, but this is one of their primary functions, so IMO this is a bug in OS/2 GCC implementation and should be reported and fixed. Otherwise it defeats the purpose of disk option file almost completely. Brgds, Viktor On 2010 Feb 12, at 13:03, David Arturo Macias Corona wrote: > Maurilio: > > >I've reviewed your messages, I think 32K is environment size limit for > >OS/2 processes; so, maybe os2gcc and/or ld receive something as an > >envvar and this is now bigger than 32Kb :( > > Thanks for your time and efforts > If what you say is true, then is a bad new > > Solution may be to use temporary files on disk in place of envvars, but again > os2gcc must be changed and re-build > > Current __dyn__.tmp file sizes are: > > os2gcc335 a.out: > E:\harbour102\harbour\src\dynlib\obj\os2\gcc 29,242 > E:\harbour102\harbour\src\dynlib\mt\obj\os2\gcc 31,143 > > os2gcc442 OMF: > E:\harbour102\harbour\src\dynlib\obj\os2\gccomf 31,087 > E:\harbour102\harbour\src\dynlib\mt\obj\os2\gccomf 32,985 > > OpenWatcom: > E:\harbour102\harbour\src\dynlib\obj\os2\watcom 39,769 > E:\harbour102\harbour\src\dynlib\mt\obj\os2\watcom 41,656 > > > For today and os2gcc, only os2gcc442OMF-mt are bigger than: > 2**15 = 2**(16-1) = 32768 bytes = 32 Kbytes > and fail to build harbourm.dll > > os2gcc335 a.out - mt are near to fail too > > David Macias > > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour