Re: moving binary port as installed from one system to another (openoffice.org-2 amd64)
On 3/15/07, Steve Franks [EMAIL PROTECTED] wrote: No idea why there isn't an openoffice pkg yet for 6.2/amd64, but some of us are running that on laptops, not servers, and we like to do things like edit documents. ftp://ooopackages.good-day.net/pub/OpenOffice.org/FreeBSD/ Steve -- Pietro Cerutti - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
moving binary port as installed from one system to another (openoffice.org-2 amd64)
No idea why there isn't an openoffice pkg yet for 6.2/amd64, but some of us are running that on laptops, not servers, and we like to do things like edit documents. Broke down and built the port, which took about 24 hours (after I found installed all dependent packages [built dependencies for a couple days before that]), but it went well and functions. I'd really like to skip doing that on my other system, however. So, is there a standard description of what files, folders, etc, make up a package, other than the makefile, such that I can copy openoffice to my other machine(s)? For that matter, is there a standardized way to build a pkg from a port, or is that entirely up to the port maintainer? See where I'm headed? Or am I hopelessly naive? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: moving binary port as installed from one system to another (openoffice.org-2 amd64)
On Wednesday 14 March 2007 16:21, Steve Franks said: No idea why there isn't an openoffice pkg yet for 6.2/amd64, but some of us are running that on laptops, not servers, and we like to do things like edit documents. Broke down and built the port, which took about 24 hours (after I found installed all dependent packages [built dependencies for a couple days before that]), but it went well and functions. I'd really like to skip doing that on my other system, however. So, is there a standard description of what files, folders, etc, make up a package, other than the makefile, such that I can copy openoffice to my other machine(s)? For that matter, is there a standardized way to build a pkg from a port, or is that entirely up to the port maintainer? See where I'm headed? Or am I hopelessly naive? Steve You can use 'make package' from the port directory you want to package. That will build a package from the port with the options you selected and put it in /usr/ports/packages/All/your_package.tgz. You can then copy and install it on another machine with 'pkg_add'. Cheers, Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- pgpdyq1BpS0wU.pgp Description: PGP signature
OpenOffice.org on amd64
I tried to run OpenOffice.org on my amd64 desk, but there wasn't amd64-package of 2.0.2, so I installed i386 version. As I understand, binary i386-emulation compiled into kernel should allow me to run any i386 application by concept. But, thereis such a problem running OOo: ---CUT--- $ openoffice.org /libexec/ld-elf.so.1: Shared object libuno_sal.so.3 not found, required by javaldx /libexec/ld-elf.so.1: Shared object libm.so.4 not found, required by pagein /libexec/ld-elf.so.1: Shared object libvcl680fi.so not found, required by soffice.bin ---CUT--- $ ls /usr/local/openoffice.org-2.0.2.rc2/program/lib*.so* /usr/local/openoffice.org-2.0.2.rc2/program/libuno_sal.so.3 /usr/local/openoffice.org-2.0.2.rc2/program/libvcl680fi.so $ ls /lib/libm* /lib/libm.so.4 /lib/libmd.so.3 $ export LD_LIBRARY_PATH=/usr/local/openoffice.org-2.0.2.rc2/program $ openoffice.org /libexec/ld-elf.so.1: Shared object libuno_sal.so.3 not found, required by javaldx /libexec/ld-elf.so.1: Shared object libm.so.4 not found, required by pagein /libexec/ld-elf.so.1: Shared object libvcl680fi.so not found, required by soffice.bin $ ldconfig -m /usr/local/openoffice.org-2.0.2.rc2/program $ openoffice.org /libexec/ld-elf.so.1: Shared object libuno_sal.so.3 not found, required by javaldx /libexec/ld-elf.so.1: Shared object libm.so.4 not found, required by pagein /libexec/ld-elf.so.1: Shared object libvcl680fi.so not found, required by soffice.bin $ ldd /usr/local/openoffice.org-2.0.2.rc2/program/soffice.bin ldd: /usr/local/openoffice.org-2.0.2.rc2/program/soffice.bin: can't read program header ldd: /usr/local/openoffice.org-2.0.2.rc2/program/soffice.bin: not a dynamic executable $ file /usr/local/openoffice.org-2.0.2.rc2/program/soffice.bin /usr/local/openoffice.org-2.0.2.rc2/program/soffice.bin: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), stripped $ uname -r 6.1-PRERELEASE Does anybody know what is the clue? Seems like linker cannot correctly define file type and it's dependencies (but how does it not find some libs!?). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
