2010/7/16 Russ Allbery r...@debian.org:
If so, you won't be alone, and I'm sure we'll end up with a transition
plan.
I've been holding off on adding symbols for C++ libraries until the
support for C++ symbol patterns is in stable for exactly that reason. It
resolves the problem of
Liang Guo bluestonech...@gmail.com writes:
Is it acceptable that a library come without symbols file?
Yes. It's still optional, particularly for C++ libraries I think.
I found my package will generate different symbols in different
platform(i386 amd64), if I use symbols generated in amd64,
[...]
I found my package will generate different symbols in different
platform(i386 amd64), if I use symbols generated in amd64, it will not
compile in i386; if I use symbols generated in i386, it will not compile
in amd64, I have not test other platform, but I think it may have the
* Russ Allbery r...@debian.org, 2010-07-15, 21:19:
Does it mean when using different compiler, the SAME library source code
will generate different symbols?
Yes. C++ mangling can vary between compiler versions,
For GCC, mangling rules has been stable for a while (modulo bugs, like
va_list
On Fri, Jul 16, 2010 at 11:32:36AM +0800, Liang Guo wrote:
Hi, ALL,
My package(sunpinyin) is compiled with g++ 4.4, and it's symbols file
is generated by dpkg-gensymbols, when I switch g++ to 4.3, and compile
package, I get the following error:
(snip)
dh_makeshlibs: dpkg-gensymbols
Hi, ALL,
My package(sunpinyin) is compiled with g++ 4.4, and it's symbols file
is generated by dpkg-gensymbols, when I switch g++ to 4.3, and compile
package, I get the following error:
dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols
file: see diff output below
Liang Guo bluestonech...@gmail.com writes:
Does it mean when using different compiler, the SAME library source code
will generate different symbols?
Yes. C++ mangling can vary between compiler versions, as can what symbols
are generated in a shared library depending on what the shared libray
2010/7/16 Russ Allbery r...@debian.org:
If it does, which compiler should I use to compile my packages and to
generate symbols?
Whatever the current Debian default compiler as installed by
build-essential is.
Current build-essential depends on g++ (= 4:4.4.3), so I should use g++ 4.4.3.
Liang Guo bluestonech...@gmail.com writes:
2010/7/16 Russ Allbery r...@debian.org:
If it does, which compiler should I use to compile my packages and to
generate symbols?
Whatever the current Debian default compiler as installed by
build-essential is.
Current build-essential depends on
9 matches
Mail list logo
