Opened 14 years ago
Closed 12 years ago
#71 closed defect (wontfix)
unnecessary dependence on gccxxx.dll
Reported by: | dryeo | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | general | Version: | 1.6.0-b19 RC |
Severity: | low | Keywords: | |
Cc: | daveryeo@… |
Description
Java includes a dependence on ftp://ftp.netlabs.org/pub/gcc/gcc4core.wpi. This can result in multiple installs of these DLLs, wasted bandwidth downloading them yet again for very little benefit.
Simple solution is to set GCCOPT='-static-libgcc'
This will statically link the couple of small functions that may be needed.
Change History (3)
comment:1 by , 14 years ago
Severity: | → low |
---|
comment:2 by , 14 years ago
We've been using it in Mozilla since GCC 3.4.6. Large C++ program that has been built static, shared and libxul (basically one large DLL).
Also don't know if Paul updated his patches but Bird relicensed his code as GPL with the linking exception.
comment:3 by , 12 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
for me this makes no sense, as the gcc4core.wpi is needed by a lot apps anyway. and with rpm this is afaik no issue at all.
The theoretical problem with -static-libgcc is that if libgcc contains any shared data and the application involves C++ DLLs, it will not work right (the EXE and each DLL will have its own copy of this shared data in case of static linking).
So I don't mind adding this switch when I get a proof that the shared data in libgcc is not the case for OS/2. I have to study the libgcc sources to find it out.