With the package CD mounted as /mnt/cdrom and PKGDIR set accordingly, I get: checking the installed libc is at least version 2.1.1... checked checking for bison... /usr/bin/bison checking the bison version... checked (/usr/bin/bison 1.875d) checking for flex... /usr/bin/flex checking for patch... /usr/bin/patch checking for zip... /usr/bin/zip checking for libart-2.0 >= 2.3.13 ... yes checking LIBART_CFLAGS... -I/usr/include/libart-2.0 checking LIBART_LIBS... -lart_lgpl_2 checking for libstartup-notification-1.0 >= 0.5 ... yes checking LIBSN_CFLAGS... -I/usr/include/startup-notification-1.0 checking LIBSN_LIBS... -lstartup-notification-1 checking whether to build mozilla connectivity... yes checking whether to include FontOOo... yes checking whether to use system libmspack... no checking which nas to use... internal checking which curl to use... external checking curl/curl.h usability... yes checking curl/curl.h presence... yes checking for curl/curl.h... yes checking for curl_easy_setopt in -lcurl... no configure: error: curl not found or functional !!! ERROR: app-office/openoffice-1.1.4-r1 failed. !!! Function src_compile, Line 346, Exitcode 1 Doing which curl turns up a /usr/bin/curl I'm trying to configure a pretty standard Linux system with Gentoo and have run into two bugs trying to install gnumeric and now this one trying to install openoffice (which I attempted because I can't install gnumeric and need a spreadsheet). I admit this is a small sample, but it makes me wonder about the Gentoo package QA process. I'm a newcomer to Gentoo -- this install is for evaluation purposes -- and this much trouble installing standard packages really gives me pause. Reproducible: Always Steps to Reproduce: 1. 2. 3.
We don't provide openoffice as a binary package, but openoffice-bin...
You are correct that the binary package on the packages cd is called openoffice- bin and, indeed, that package installs and seems to work. But I issued the command emerge --usepkg app-office/openoffice and there is such a package, apparently broken. Why are there openoffice and openoffice-bin packages? Why is openoffice-bin apparently the correct package to request when you want openoffice (the name of the system, after all, is openoffice, not openoffice-bin)? If openoffice-bin is the right thing and openoffice is broken, why not remove the latter and rename the former to openoffice, which would be a lot less confusing to newcomers like me?
You're missing the point here. Gentoo is source-based. Using "openoffice" does the source-based installation, and not the package installation. There being a package has nothig to do with the naming. There are two packages in Gentoo, that are *not* equivalent. These are "openoffice" and "openoffice-bin". Doing an "emerge --usepkg openoffice" checks that there is an openoffice package, then, when it doesn't see one, downloads the sources and tries to compile the package. Doing an "emerge --usepkg openoffice-bin" sees that there is a package and installs it. If there wasn't one, it would download the *binaries* and install it. All binary packages in Gentoo that have a source equivalent are marked with -bin, hence the openoffice-bin package naming. You can't use openoffice on a binary/GRP installation, but you can use openoffice-bin, as that is the only one that we provide. Were you to being doing a source-based installtion, you could use either openoffice, or openoffice-bin, and either would work, but they would give different output, as one would be compiled by you, using your CFLAGS/USE flags on your system, the other by the OpenOffice team using their configure choices and optimizations. Does it make sense now?
The point I missed is that apparently -bin is the Gentoo naming convention indicating a binary package. However, in your attempt to get me unconfused (thank you), an issue remains unaddressed. That is that emerge --usepkg app-office/openoffice attempted to load the *source* package 'openoffice' and that failed, as described in my original bug report.
Correct. In doing a binary installtion, you can't mix in source packages quite as easily. However, the package definitely should be sure that curl is installed properly. I'm going to reassign this to the openoffice team.
I actually don't quite see, how this is an openoffice-bug. We have a correct dependency on curl, so I'm not sure what to do here.
I'm closing this, as I said this is not a problem of OOo and nothing we can do here. If someone else wants to take this, reassign the bug and reopen it
