Re: Troubles using apbuild
Isak Savo <[email protected]> Thu, 19 Mar 2009 19:25:50 +0100
| Newsgroups | gmane.comp.autopackage.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Mar 19, 2009 at 6:47 PM, Mathieu Cadet <[email protected]> wrote: > Hi, > > I've managed to fix those errors and mono's building fine on x86 now. > > However, it doesn't build on 64bit systems: > > [...] > ./.libs/libmonoruntime.a(verify.o): In function `is_valid_cls_ident': > /usr/src/packages/BUILD/mono-2.2/mono/metadata/verify.c:1015: > undefined reference to `__ctype_b@GLIBC_2.0' > /usr/src/packages/BUILD/mono-2.2/mono/metadata/verify.c:1015: > undefined reference to `__ctype_b@GLIBC_2.0' > [...] > > Any ideas? Is there a compiler flag I can use to make those errors go away? 64bit systems don't need the level of backward compatibility that apbuild tries to enforce. With 64bit, glibc wiped the plate clean and started fresh from 2.something so there are really not many old systems to support. Perhaps it's time to give apbuild an option to say which minimum GLIBC version to target? Would be a nice thing to have -Isak --------------------------------------------------------------------- To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected] For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]