Thanks for the explanations Stuart. I didn't look into the problem too much before trying to build the port because I figured it might be a problem with the package. After your reply I realize this is a tough situation.
> > Is libreoffice known to be broken on AMD64 5.2-stable? > > I don't have anything running 5.2 at present (everything's -current here) but > in practice libreoffice (and chrome which has the same problem) does usually > run OK so I *think* the screen not being painted properly is probably not > related to the conflicting symbols which trigger the "size mismatch". Looks like the libreoffice version numbers on current and stable differ quite a bit so I'm not sure if we can draw any conclusions based on what works in current. It would be helpful to know if anybody else is running it without issues in stable on AMD64 though. > > How much space should I allocate to /usr/ports to be able to build anything > > in the tree at this point? Looking at the man page for ports and bsd.port.mk > > I am not sure whether moving the work directory elsewhere (I have plenty of > > space in var) would work or whether everything needs to be in one tree. > > You can happily use a work directory outside of /usr/ports; set WRKOBJDIR > in /etc/mk.conf. I do this on pretty much every machine I build ports on > (the default auto-partitioning layout is geared towards people using > packages rather than building from ports). I never take the auto layout either but in the past 5G ports has been plenty. I didn't build any behemoths like libreoffice obviously! Thanks for confirming WRKOBJDIR will do the trick. I was about to try it but wasn't sure I understood the man page warnings about stuff out of tree not building correctly 100% of the time, given this port was already questionable to begin with. I didn't want to introduce any other source of possible screwups while attempting to get a good copy. > However: I don't think a self-built libreoffice is likely to work > any better, and building it is rather painful. This makes sense after your explanation above. > Probably better to look around and see what more information you can find > about what's happening. Describing the screen painting problem might be > useful (i.e. what you do, what you see). And there are other things you > can try - is it tied to a specific window manager, for example? Basically when it starts up it leaves a major U-shaped space on the screen unpainted. Whatever was there before shows up and doesn't get covered by libreoffice. At first I thought it was the splash screen like OO used to have but that is square, not this bizarre T shape. I was able to do some things like open a new document but it was not operating like my old OO normally did, some things were just weird. It feels sick, something is definitely not right. Since I figured the package was broken I didn't pay too much attention to the details and from experience it seems like if a port is broken the answer is to run -current anyway so I figured if it was broken it wasn't going to be useful to give too much detail on it. Maybe I am wrong but that's what I have seen in the past on the mailing list. I just converted my main desktop to OpenBSD because I was so happy with it on my Loongson. I used OpenBSD years ago and drifted away from it because I was multibooting too many OS but came back recently because of the quality and because I needed something to run on a Loongson box. After that I figured it was time to reduce the number of OS I have running here and I am not happy with the directions Linux is going in and the other BSD projects seem to be struggling so OpenBSD won. I am not bashing any of those projects since I have used them all productively in the past and appreciate all the work that goes into them but everybody has his own preferences right? I do want to say thank you again to all the OpenBSD people because you put out a great OS and I can see people really pay attention to detail and usually give a damn and take it hard if something isn't right. The flaming can suck but on the other hand bullshit is significantly reduced and quality stays up. Anyway I had no way to test ahead of time to see if the apps I need will work since this is a one-off box with el-cheapo components, couldn't emulate it on qemu or vbox etc. so I just winged it. I'm going to see if I have better luck with the last release of OO on another system that libreoffice isn't available for. At this point I need to be able to edit some old doc. If you think the port from current will build and run on stable I have no problem trying it. This box runs pretty good (takes like 45/30 minutes to build userland/xenocara) and it's no problem to build big ports now that you said I can move the work directory. Thanks alot for your reply. /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary / \ http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
