David, David Arturo Macias Corona wrote: > Confirmed. The guilty is length of command line > So here we are again :(
> gcc -Zomf -shared -L../../../../../lib/os2/gcc -o > ../../../../../bin/os2/gcc/harbour.dll @__dyn__.tmp __dyn__.def -lsocket > Warning! W1058: file ldvJjRLI.: line(613): protmode option not valid for > an OS/2 EMX dynamic link library Maybe .a out files simply don't take it into account? > Note: using $(DYNNAME) does not include .dll extension, so I suppose it > is added by default and not due Harbour definitions > @$(ECHO) LIBRARY $(DYNNAME) INITINSTANCE TERMINSTANCE >> __dyn__.def > No, it is used because library name is not .dll file name; it has to be without .dll extension or otherwise import library does not work. > and harbourm.dll build fine, with different size than harbour.dll > Same warning for protmode in harbourm.dll > > So the reason for emxomfld failure is due to length of long list of > object files in section: > As such I say that for the time being we keep .a out. :) BTW, when using .a out we use a link file (__dyn__.tmp) so where is the line length limit reached? > Viktor, Maurilio, Przemek: > any idea to overcome this limit ? > You could try to contact Paul Smedley and/or Knut Osmundsen and see if they can fix this issue. Maurilio. -- __________ | | | |__| Maurilio Longo |_|_|_|____| farmaconsult s.r.l. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
