On Sun, Apr 10, 2011 at 09:49:05AM -0300, Henrique de Moraes Holschuh wrote: > On Sun, 10 Apr 2011, Steve Langasek wrote: > > multiarch. The attached patch has been applied in Ubuntu for this issue, > > correcting this call to use --with-com_err with no argument to get the > > default search path.
> Has this been triple-checked to do the right thing? No, only double-checked. I had reviewed the source of configure.in which was how I spotted the difference between --with-com_err and --with-com_err=/usr; but it turns out that what's actually needed is --with-com_err= rather than --with-com_err since --with-com_err is --equivalent to --with-com_err=yes. Thanks for making me take a third look at this. > I used to have to employ extremely hard measures (aka rm -fr et/ in > debian/rules clean) to convince the Cyrus build to not do anything > extremely hazardous, such as using pieces of system com-err and pieces of > cyrus com-err. I *really* would not trust configure to not do something > idiotic without directly checking the object files and poisoning the local > copies of com-err to fail any build that touches them, so as to make sure > everything is doing what it is supposed to... After switching to --with-com_err=, I've confirmed that there are no longer any mentions of libcom_err.a in the build log. So I'm personally convinced that this is sufficient, but of course if you would prefer a fix-upstream-harder solution you are welcome to it. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
