Bug#336591: wvstreams: FTBFS with openssl 0.9.8

2005-11-01 Thread James A. Morrison

 What happens if you remove -pipe?

-- 
Thanks,
Jim

http://www.csclub.uwaterloo.ca/~ja2morri/
http://phython.blogspot.com
http://open.nit.ca/wiki/?page=jim


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#325247: libwvstreams4.0-qt: uninstallable because of missing libqt3c102-mt

2005-09-09 Thread James A. Morrison

Simon Law [EMAIL PROTECTED] writes:

 On Fri, Sep 09, 2005 at 01:03:37PM -0700, Steve Langasek wrote:
 wvstreams is implemented in C++.  Where are the package renames for the
 C++ ABI transition?
 
 Simon, is it really true that none of the wvstreams libraries use code
 from libstdc++?  (None of the packages have dependencies on libstdc++5)
 I guess this is possible, but at least one of the library packages has
 undefined symbols, which makes it unsuitable for use by any sort of DSO
 plugin:

 WvStreams does not use code from libstdc++, which we carefully avoid
 compiling in, by linking with gcc (not g++).

 I take it you changed this back to using gcc for linking?  At some point I
had the debian package link with g++.

 Why ldd thinks we do is slightly beyond me.

 As for WvHashTableBase, this is probably some place where an
 interlibrary dependency has snuck in somehow.  I don't see it in my
 build of WvStreams 5, so I'm not going to get too stressed out about it.

 -- 
 Simon Law http://www.law.yi.org/~sfllaw/




-- 
Thanks,
Jim

http://www.csclub.uwaterloo.ca/~ja2morri/
http://phython.blogspot.com
http://open.nit.ca/wiki/?page=jim


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#301168: wvstreams FTBFS: build-dependency on non-existent package

2005-03-24 Thread James A. Morrison
Steve Langasek [EMAIL PROTECTED] writes:

 Package: wvstreams
 Source: wvstreams
 Version: 4.0.2-1
 Severity: serious
 
* Acknowledge NMUs.  (Closes: #292618, #297694, #297554, #286593, #289237)
* We now depend on XPLC 0.3.11.
 
 Lovely.  After four consecutive NMUs to try to get the last upstream version
 into a releasable state, you've just uploaded another new upstream version
 which has a trivially visible RC bug: build-depending on a version of XPLC
 that isn't in the archive.
 
 Looks like sarge users will have to wait even longer now for fixed modem
 support.
 

 I'll upload a fixed package this morning.  Sorry for the breakage.


-- 
Thanks,
Jim

http://www.student.cs.uwaterloo.ca/~ja2morri/
http://phython.blogspot.com
http://open.nit.ca/wiki/?page=jim


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]