On Saturday, Jun 14, 2003, at 18:45 US/Eastern, Matt Zimmerman wrote:
My two questions were:
1) Why did dpkg-buildpackage wind up compiling with the wrong
compiler? Isn't there a C++ transition plan that should
prevent that.
python-apt will, by default, use the de
On Sun, Jun 15, 2003 at 03:23:37PM -0400, Anthony DeRobertis wrote:
> In a perfect world, somehow the correct gcc would be used (to make sure
> C++ ABI problems don't happen). Not sure if we can have that perfect world
> or not; see below.
No, we can't. Not today, and definitely not a year ago.
On Saturday, Jun 14, 2003, at 19:17 US/Eastern, Matt Zimmerman wrote:
This was before woody released, before there was
any kind of C++ ABI transition plan, before there was even a g++-3.2
in the
archive. Surely you aren't suggesting that last year's
build-dependencies
should have anticipated
On Sunday, Jun 15, 2003, at 15:50 US/Eastern, Matt Zimmerman wrote:
Er, no. Those binaries would work perfectly fine if you had built apt
with
the same C++ ABI. But I can't specify in a build-dependency "oh, and
your
apt must be built with the same C++ ABI". I _certainly_ can't do so
retroa
4 matches
Mail list logo
