On Dec 24, 2003, at 8:18 PM, Ben Hines wrote:
Depends on what variables the buildsystem honors.
Usually
SetLIBS: -lstdc++
or maybe
SetLDFLAGS: -lstdc++
etc.
But usally you'd want to be linking with "g++" instead of "gcc" to fix
the c++ link problem.
Actually, I only need SetLDFLAGS: -lstdc++.
Le 25 déc. 2003, à 06:21, Ben Hines a écrit :
Yes, it does check that on the deb file, but most folks probably don't
realize that deb files can be validated. Its also easy to miss changes
when updating packages.
Apropos validation, I've found 2 packages from those I've installed
that do not val
I totally agree with this, the pkg maintainers should be making sure
the -L/sw/lib and bogus deps don't make the .la files, fixing
pilot-link9 wasn't an easy task because of this, I had to disable iconv
support.
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Costabel wrote:
| Ben Hines wrote:
|
|>
|> On Dec 22, 2003, at 4:50 AM, Martin Costabel wrote:
|>
|>> Solutions: Either one allows gettext-dev to Depend on libiconv-dev
|>> (but this not only violates policy but may also break bootstrapping,
|>>
Ben Hines wrote:
On Dec 22, 2003, at 4:50 AM, Martin Costabel wrote:
Solutions: Either one allows gettext-dev to Depend on libiconv-dev
(but this not only violates policy but may also break bootstrapping,
because gettext-dev might be needed before libiconv is built), or all
packages that are s
Ben Hines wrote:
On Dec 22, 2003, at 4:50 AM, Martin Costabel wrote:
by this problem (and this is hard to detect and concerns potentially
many packages) would need a BuildDepends on both gettext-dev and
libiconv-dev.
Yes, that is the answer. Any packages which don't should be fixed. Feel
free
