[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] libtool ignores unresolved symbols despite -no-undefined fla
Re: [PATCH] libtool ignores unresolved symbols despite -no-undefined flag
Sun, 15 Nov 2009 14:36:41 +0100
* Torsten Landschoff wrote on Sun, Nov 15, 2009 at 04:16:34AM CET:
> I think, GNU libtool should indead report an error if building with
> -no-undefined even on systems where undefined symbols are allowed. That
> way, one will notice during development that a feature is used that
> may not be available on the target system.
Yes, this is a good idea. The problem with this is that it frequently
happens that some of the system libraries like glibc have undefined
symbols themselves, on purpose, subverting this nice feature. (The
symbols are then somehow satisfied at runtime.)
At least that's how it used to be last time we tried this. I haven't
checked this in a long time. It may be that this only mattered for
C++ or so. But anyway changing this would require somebody to dig
this out and verify that the issue is gone for the systems/libc
versions where we enable it.
FWIW, in your patch series, I'd squash patches 1,2,5, and patches 3,4.
A Fortran test would be good.
Please also note that in order to accept nontrivial patches, we need
copyright assignment papers from you (details off-list). If that won't
work out for you, then it is better if you don't post patches, but only
explain needed changes, so that there is no doubt someone else
reimplementing them causes copyright issues.
Thanks for the report and patches,