From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-02-13 08:37:37
On Monday 13 February 2006 16:20, Markus Schöpflin wrote:
> > BTW, I wonder if "-x c" is present, too?
> I knew you would ask. ;-) But according to the man page and confirmed by my
> experiments it's only present in the Linux version of cxx and not in the
> Tru64 version.
Ok, then never mind.
> > Because the 'b' symbol is not found. So, the linker differs in behaviour
> > from GNU linker, that allows shared library to contain unresolved
> > references and does not produce even a warning.
> > This leaves two questions:
> > 1. Is there an option to suppress the warning? I saw some
> > "-expect_unresolved" options in V1 toolset file.
> Here is an excerpt from the ld manual:
> -expect_unresolved pattern
> I added -expect_unresolved * to the command line generated by the link.dll
> action, the test now passes. The change is committed.
> > 2. Should such option be always used, or only for this test? I'd prefer
> > to always used it, but I'm so accustomed to GNU behaviour that my opinion
> > does not matters much.
> I think it's OK to add it when linking dynamic libraries.
> I reran the full regression tests and there is only one failure left now.
> Seems like you need some actual declaration in there to make the warning go
Yea, I've comitted a supposed fix.
Now that V2 regressions are in shape, can you run C++ Boost regressions as
Thank you very much for the quick feedback! The toolset went from
non-existance to fully working in less then a week, which is rather amazing.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk