Summary: | app-office/openoffice-3.0.0 - ooo300-m9/bridges/source/cpp_uno/gcc3_linux_x86-64/abi.cxx:76: error: '__int128_t' does not name a type | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | denis <denisr> |
Component: | New packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
denis
2009-01-16 16:45:01 UTC
dtardon->denisr: Excuse me, but exactly what system (architecture) do you have (or think you have)? You've reported it against x86 (which is also what the 'emerge --info' listing says), but you're trying to compile openoffice for amd64 (or x86_64, which is what this arch is known like outside of gentoo).... The problematic file shouldn't be--and from quick peek into appropriate makefile.mk it isn't, indeed--compiled on any platform outside of amd64, so I think the problem is actually in your configuration, not in openoffice. (In reply to comment #1) > dtardon->denisr: Excuse me, but exactly what system (architecture) do you have > (or think you have)? You've reported it against x86 (which is also what the > 'emerge --info' listing says), but you're trying to compile openoffice for > amd64 (or x86_64, which is what this arch is known like outside of gentoo).... > The problematic file shouldn't be--and from quick peek into appropriate > makefile.mk it isn't, indeed--compiled on any platform outside of amd64, so I > think the problem is actually in your configuration, not in openoffice. > I'm compiling it inside chroot x86 system, and so I'm trying to compile for x86. All other packages emerged this way for x86. The server on which I'm emerging the new Gentoo is actually x86_64, but everything inside the chroot environment is a proper x86 Gentoo system, which I've emerged up from stage3, all libs,compiler, apps etc ... Thus emerge --info shows all the right info about the x86 chroot environment. I don't know therefore why OO build thinks its being compiled on x86_64 ? Note that I have no problem while emering other applications this way (inside this chroot'ed x86 environment). The reason I noted the x86_64 fact previously is because on top of the emerge --info list, System uname shows kernel for x86_64, the running system kernel. (I have proc mounted in my chroot). May be I'm not correct about reporting this as bug in the OO building process, but since no other build so far got confused about which arch its being built for, it seems something OO specific in the build process here which fails. Everything else produced the intended x86 libs and apps. (In reply to comment #2) > (In reply to comment #1) > > dtardon->denisr: Excuse me, but exactly what system (architecture) do you have > > (or think you have)? You've reported it against x86 (which is also what the > > 'emerge --info' listing says), but you're trying to compile openoffice for > > amd64 (or x86_64, which is what this arch is known like outside of gentoo).... > > The problematic file shouldn't be--and from quick peek into appropriate > > makefile.mk it isn't, indeed--compiled on any platform outside of amd64, so I > > think the problem is actually in your configuration, not in openoffice. > > > > I'm compiling it inside chroot x86 system, and so I'm trying to compile for > x86. All other packages emerged this way for x86. > The server on which I'm emerging the new Gentoo is actually x86_64, but > everything inside the chroot environment is a proper x86 Gentoo system, which > I've emerged up from stage3, all libs,compiler, apps etc ... > > Thus emerge --info shows all the right info about the x86 chroot environment. > I don't know therefore why OO build thinks its being compiled on x86_64 ? > > Note that I have no problem while emering other applications this way (inside > this chroot'ed x86 environment). > > The reason I noted the x86_64 fact previously is because on top of the emerge > --info list, System uname shows kernel for x86_64, the running system kernel. > (I have proc mounted in my chroot). > > May be I'm not correct about reporting this as bug in the OO building process, > but since no other build so far got confused about which arch its being built > for, it seems something OO specific in the build process here which fails. > Everything else produced the intended x86 libs and apps. > Perhaps setarch i686 is in order before compiling it ... Ooopsie, have to try it (pitty have to do this after reporting the bug) and see if it fixes my problem (In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > dtardon->denisr: Excuse me, but exactly what system (architecture) do you have > > > (or think you have)? You've reported it against x86 (which is also what the > > > 'emerge --info' listing says), but you're trying to compile openoffice for > > > amd64 (or x86_64, which is what this arch is known like outside of gentoo).... > > > The problematic file shouldn't be--and from quick peek into appropriate > > > makefile.mk it isn't, indeed--compiled on any platform outside of amd64, so I > > > think the problem is actually in your configuration, not in openoffice. > > > > > > > I'm compiling it inside chroot x86 system, and so I'm trying to compile for > > x86. All other packages emerged this way for x86. > > The server on which I'm emerging the new Gentoo is actually x86_64, but > > everything inside the chroot environment is a proper x86 Gentoo system, which > > I've emerged up from stage3, all libs,compiler, apps etc ... > > > > Thus emerge --info shows all the right info about the x86 chroot environment. > > I don't know therefore why OO build thinks its being compiled on x86_64 ? > > > > Note that I have no problem while emering other applications this way (inside > > this chroot'ed x86 environment). > > > > The reason I noted the x86_64 fact previously is because on top of the emerge > > --info list, System uname shows kernel for x86_64, the running system kernel. > > (I have proc mounted in my chroot). > > > > May be I'm not correct about reporting this as bug in the OO building process, > > but since no other build so far got confused about which arch its being built > > for, it seems something OO specific in the build process here which fails. > > Everything else produced the intended x86 libs and apps. > > > > Perhaps setarch i686 is in order before compiling it ... > > Ooopsie, have to try it (pitty have to do this after reporting the bug) and see > if it fixes my problem > Ok, what's necessary to emerge it here successfully is chroot /my/newx86system setarch i686 Then it emerges fine. Hmm, strange other packages did not require this, but I guess its not a bug in OO build process. Sorry for reporting this, my bad Thx a lot. I had the same problem. It made me crazy, because I couldn't get a logical explication for that strange behaviour. With setarch i686 it's working. Thanx again. This is a user-side system-configuration problem, nothing we can do here, so closing |