Linking many .o files together (instead of compiling the .jar file directly)

Rutger Ovidius ovid@mailandnews.com
Sat Oct 18 15:15:00 GMT 2003


Hi,
When I am forced to compile a .jar file by extracting its individual .class 
files, I end up with a ton of .o files.
Is there a way I can combine them to one big .o file representing what would 
have been compiled if the .jar file compilation had been successful?
Many .jar files on windows which compiled fine with 3.3.1, now fail in a 
similar way on 3.4 with an error (replacing the symbol name) like:
C:\DOCUME~1\v\LOCALS~1\Temp/cc0Maaaa.s: Assembler messages:
C:\DOCUME~1\v\LOCALS~1\Temp/cc0Maaaa.s:94227: Error: symbol 
`__GLOBAL__I__ZN3org7eclipse4core8internal4boot16URLConte
ntFilter6class$E' is already defined
These files will rely on other .jar libraries from the CLASSPATH.
ld -o big.o *.o won't work.
gcj --CLASSPATH=x;x;x -o big.o *.o fails too.
Any hints? Thanks. 


More information about the Java mailing list

AltStyle によって変換されたページ (->オリジナル) /