On Tue, Jun 28, 2011 at 15:54, Ruben Molina <[email protected]> wrote: > Thanks for your help! Looks like it was wrong to assume a common set of > symbols for all the arches. May I ask you to remove debian/*.symbols, > and try to build the package again?
Set in your debian/rules this instead of removal: export DPKG_GENSYMBOLS_CHECK_LEVEL=0 It will cause dpkg-gensymbols to proceed regardless of the symbol-outcome which is quiet handy to collect architecture dependent symbols in the first upload and to see other differences based on toolchain (e.g. c++ lib tend to generate different optional symbols with different compiler versions). btw: Without looking at the source: Architecture dependent symbols are e.g. all methods with size_t (or its sibling ssize_t) or va_list as parameter. Best regards David Kalnischkies -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
