I'm configuring a dual Opteron at the office using the x86_64 live cd. All the builds went really well until I hit xfree. The xfree build fails with an Access Violation message: chmod: /xfree-4.3.0-r3/work/xc/fonts/scaleb/CID/fonts.dir Looks to me it's a makefile issue but I don't have the time to poke around. I'd appreciate any help. Reproducible: Always Steps to Reproduce: 1.emerge xfree 2. 3. Actual Results: Access Violation message: chmod: /xfree-4.3.0-r3/work/xc/fonts/scaleb/CID/fonts.dir The system is a dual 2.0Ghz Opteron using the x86_64 architecture: CHOST="x86_64-pc-linux-gnu" CFLAGS="-O2 -fPIC -pipe" ACCEPT_KEYWORDS="~amd64" I'm not detailing HW because it doesn't seem to be relevant.
Oops, the correct error message is: chmod: /xfree-4.3.0-r3/work/xc/fonts/scaled/CID/fonts.dir
yeah, this is a known bug if you cd /usr/portage/x11-base/xfree ebuild xfree-4.3.0-r3 install ebuild xfree-4.3.0-r3 qmerge that will get you by for now. Hopefully I'll have a patch committed for that access violation this weekend. It seems to happen on every amd64 system we've seen, so it's definately an amd64 bug.
Thanks Brad, that did the trick!
Hi Brad, Got a fix for the sandbox issue yet? If it's an xfree patch, just attach it here and I'll add it to the patchset. Otherwise maybe this should be reassigned to dev-portage.
This seems to have disappeared recently. I have had no reports of it, and have reemerged xfree86 multiple times recently, and on new builds (within a chroot). I guess whatever it was has been resolved, I'd really be interested to know what it was though. I'm hesitant to close it, but you're welcome to if other platforms appear to be ok. -Brad
Nothing really changed in xfree, I'd guess it's a portage issue. I'll close since it's not reproduceable.
