The above-referenced libboost issue #424038 may take a while to be
resolved, and it isn't clear that -lboost_regex will come back once it
has been resolved. However, we don't need to wait to resolve the FTBFS
bug. We can restore the existing behaviour by changing the link from
-lboost_regex to -l
Can this bug's title be changed to "Source package contains useless
files", and accordingly its severity be reduced to minor or wishlist ?
pjrm.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Passing through `expand -t 4' and then appending a colon to the `if'
condition of line 371 fixes the problem better than the suggested
"noisy" patch.
Of course, "where there are bugs, there are more bugs": the fact that
it contained even compile errors shows that the original coder hadn't
tested
A "grave" bug is one serious enough to prevent the release of the
package. The description of this priority (in bug-maint-info.txt)
does mention "data loss" as a possible justification for marking a bug
as grave, but the data loss described in this bug report (qualified as
"minor" in the submitter
Messages on the mailing list suggest that gcc-4 presents a number of
problems. It may be that the best fix is to force CC=gcc-3.3 until we
have a corrected upstream version.
The above-proposed patch of making the non-gnuc version unconditional
looks wrong in light of the following comment immedia
5 matches
Mail list logo
