Re: Problem building Openoffice 3.1.1 at -current
From: Olivier Gautherot oliv...@gautherot.net Subject: Re: Problem building Openoffice 3.1.1 at -current Date: Sat, 03 Oct 2009 22:12:10 -0500 Hi folks! On Sat, Oct 3, 2009 at 7:34 PM, Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: On Mon, Sep 21, 2009 at 12:15:09PM -0700, Steve Kargl wrote: On Mon, Sep 21, 2009 at 02:39:44PM +0300, Andriy Gapon wrote: The above ln and cp were sufficient to complete my build. I haven't tested the resulting exectuables. Thanks, Andriy Rrrr The openoffice guys are trying to bundle every piece of code under the sun into their tarball in attempt to not depend upon system libraries... ... and are getting away from what they want to achieve (IMHO). OOO is as fragile as porcelain plate and still as complex to repair as nuclear u-boot. It sounds like OOO is designed to be compiled on a fresh system: I reformated a disk yesterday and the compilation of OOO just finished successfully. I loaded 8.0-RC1. As a matter of fact, I used the bundled modules - it takes longer but seems to be a bit more stable. Hi, Olivier Gautherot thanks for your e-mail. this is just a maintaing issue. if you provide some human resources I'm very happy to use python from ports tree instead. Serious problem may be that when some cws (child work space, smallest unit of development) wrt python is introduced, or when ports python is updated. Then there may be a conflict, and I'd like to ask you to fix it. Usually very easy, but sometimes very hard. thanks, -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Problem building Openoffice 3.1.1 at -current
Hi Maho Nakata, First of all, thanks for all your good work - I've been your faithful customer for several years already and really appreciate your dedication. It sounds like OOO is designed to be compiled on a fresh system: I reformated a disk yesterday and the compilation of OOO just finished successfully. I loaded 8.0-RC1. As a matter of fact, I used the bundled modules - it takes longer but seems to be a bit more stable. Hi, Olivier Gautherot thanks for your e-mail. this is just a maintaing issue. if you provide some human resources I'm very happy to use python from ports tree instead. I'll have to reissue the compilation in the data partition since I already started using the necessary space. I'll let you know. Serious problem may be that when some cws (child work space, smallest unit of development) wrt python is introduced, or when ports python is updated. Then there may be a conflict, and I'd like to ask you to fix it. Usually very easy, but sometimes very hard. From my past experience, I tend to use the ports as released and do not update the ports tree. The few times I did were tough experiences, usually ending with a complete reinstall... :-S So I'm an easy customer on the ports. System upgrades usually end up in a backup and start from scratch (which was a real exercise on a VIA motherboard). So I may be somewhat atypical... I'll let you know the results. Cheers -- Olivier Gautherot oliv...@gautherot.net Cel:+56 98 730 9361 www.gautherot.net http://www.linkedin.com/in/ogautherot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Problem building Openoffice 3.1.1 at -current
Can you guys trim your CC list? I have no interest in the stupidity of OOo in including every project under the sun into its build system. -- Steve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Problem building Openoffice 3.1.1 at -current
On Sat, Oct 3, 2009 at 7:34 PM, Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: On Mon, Sep 21, 2009 at 12:15:09PM -0700, Steve Kargl wrote: On Mon, Sep 21, 2009 at 02:39:44PM +0300, Andriy Gapon wrote: on 20/09/2009 14:38 Sam Fourman Jr. said the following: On Sun, Sep 20, 2009 at 6:26 AM, Vinicius Abrahao vinnix@gmail.com wrote: Hello dear fellows, I'm trying to upgrade my openoffice.org3 from 3.1.0 to 3.1.1, but I'm getting an strange error (associated with python). This is the error that appears many hours after I start the upgrade: I am getting this same error on FreeBSD 8.0 Beta4 any idea how to fix the build? I also had a compilation problem like this. Perhaps this is related to having python 2.6 installed on a system? Anyway, I was able to continue the build by doing the following (adjust the paths to your environment): $ ln -s /usr/obj/usr/ports/editors/openoffice.org-3/work/OOO310_m19/solver/310/unxfbsdx.pro/lib/python /usr/obj/usr/ports/editors/openoffice.org-3/work/OOO310_m19/solver/310/unxfbsdx.pro/lib/python2.6 $ cp /usr/obj/usr/ports/editors/openoffice.org-3/work/OOO310_m19/python/unxfbsdx.pro/misc/build/Python-2.6.1/build/lib.freebsd-9.0-CURRENT-amd64-2.6/*.so /usr/obj/usr/ports/editors/openoffice.org-3/work/OOO310_m19/solver/310/unxfbsdx.pro/lib/python2.6/ Maybe something else, it was a while ago. The above ln and cp were sufficient to complete my build. I haven't tested the resulting exectuables. Thanks, Andriy Rrrr The openoffice guys are trying to bundle every piece of code under the sun into their tarball in attempt to not depend upon system libraries... ... and are getting away from what they want to achieve (IMHO). OOO is as fragile as porcelain plate and still as complex to repair as nuclear u-boot. I hate OOO... With the attached patch I was able to complete the build on amd64 9-CURRENT. Will charge 9-amd64-Ports and 9-i386-Ports tinderboxes to test in a clean environment. Testing on 8-RC is still welcome. Just drop patch-OOO_XXX_CURRENT into files/ and try to rebuild. Alexey. This Worked on 9-CURRENT i386 thanks. Will this patch be included in the ports tree so it isn't broken Sam ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Problem building Openoffice 3.1.1 at -current
On Mon, Sep 21, 2009 at 12:15:09PM -0700, Steve Kargl wrote:
On Mon, Sep 21, 2009 at 02:39:44PM +0300, Andriy Gapon wrote:
on 20/09/2009 14:38 Sam Fourman Jr. said the following:
On Sun, Sep 20, 2009 at 6:26 AM, Vinicius Abrahao vinnix@gmail.com
wrote:
Hello dear fellows,
I'm trying to upgrade my openoffice.org3 from 3.1.0 to 3.1.1, but I'm
getting an strange error (associated with python).
This is the error that appears many hours after I start the upgrade:
I am getting this same error on FreeBSD 8.0 Beta4
any idea how to fix the build?
I also had a compilation problem like this.
Perhaps this is related to having python 2.6 installed on a system?
Anyway, I was able to continue the build by doing the following (adjust the
paths
to your environment):
$ ln -s
/usr/obj/usr/ports/editors/openoffice.org-3/work/OOO310_m19/solver/310/unxfbsdx.pro/lib/python
/usr/obj/usr/ports/editors/openoffice.org-3/work/OOO310_m19/solver/310/unxfbsdx.pro/lib/python2.6
$ cp
/usr/obj/usr/ports/editors/openoffice.org-3/work/OOO310_m19/python/unxfbsdx.pro/misc/build/Python-2.6.1/build/lib.freebsd-9.0-CURRENT-amd64-2.6/*.so
/usr/obj/usr/ports/editors/openoffice.org-3/work/OOO310_m19/solver/310/unxfbsdx.pro/lib/python2.6/
Maybe something else, it was a while ago.
The above ln and cp were sufficient to complete my build.
I haven't tested the resulting exectuables.
Thanks, Andriy
Rrrr
The openoffice guys are trying to bundle every piece of code under
the sun into their tarball in attempt to not depend upon system libraries...
... and are getting away from what they want to achieve (IMHO).
OOO is as fragile as porcelain plate and
still as complex to repair as nuclear u-boot.
I hate OOO...
With the attached patch I was able to complete the build on
amd64 9-CURRENT. Will charge 9-amd64-Ports and 9-i386-Ports tinderboxes
to test in a clean environment. Testing on 8-RC is still welcome.
Just drop patch-OOO_XXX_CURRENT into files/ and try to rebuild.
Alexey.
--- python/Python-2.6.1.patch.orig 2009-10-03 22:08:45.0 +0200
+++ python/Python-2.6.1.patch 2009-10-03 23:00:22.0 +0200
@@ -127,7 +127,7 @@
# Skip platforms with known problems forking from a worker thread.
# See http://bugs.python.org/issue3863.
-if sys.platform in ('freebsd4', 'freebsd5', 'freebsd6', 'os2emx'):
-+if sys.platform in ('freebsd4', 'freebsd5', 'freebsd6', 'freebsd7',
'os2emx'):
++if sys.platform in ('freebsd4', 'freebsd5', 'freebsd6', 'freebsd7',
'freebsd8', 'freebsd9', 'os2emx'):
print sys.stderr, ('Skipping test_3_join_in_forked_from_thread'
' due to known OS bugs on'), sys.platform
return
@@ -230,3 +230,603 @@
RUNSHARED=LD_LIBRARY_PATH=`pwd`:${LD_LIBRARY_PATH}
INSTSONAME=$LDLIBRARY.$SOVERSION
;;
+--- misc/Python-2.6.1/Lib/plat-freebsd9/IN.py 1970-01-01 01:00:00.0
+0100
misc/build/Python-2.6.1/Lib/plat-freebsd9/IN.py2009-10-03
22:43:13.0 +0200
+@@ -0,0 +1,571 @@
++# Generated by h2py from /usr/include/netinet/in.h
++
++# Included from sys/cdefs.h
++__GNUCLIKE_ASM = 3
++__GNUCLIKE_ASM = 2
++__GNUCLIKE___TYPEOF = 1
++__GNUCLIKE___OFFSETOF = 1
++__GNUCLIKE___SECTION = 1
++__GNUCLIKE_ATTRIBUTE_MODE_DI = 1
++__GNUCLIKE_CTOR_SECTION_HANDLING = 1
++__GNUCLIKE_BUILTIN_CONSTANT_P = 1
++__GNUCLIKE_BUILTIN_VARARGS = 1
++__GNUCLIKE_BUILTIN_STDARG = 1
++__GNUCLIKE_BUILTIN_VAALIST = 1
++__GNUC_VA_LIST_COMPATIBILITY = 1
++__GNUCLIKE_BUILTIN_NEXT_ARG = 1
++__GNUCLIKE_BUILTIN_MEMCPY = 1
++__CC_SUPPORTS_INLINE = 1
++__CC_SUPPORTS___INLINE = 1
++__CC_SUPPORTS___INLINE__ = 1
++__CC_SUPPORTS___FUNC__ = 1
++__CC_SUPPORTS_WARNING = 1
++__CC_SUPPORTS_VARADIC_XXX = 1
++__CC_SUPPORTS_DYNAMIC_ARRAY_INIT = 1
++__CC_INT_IS_32BIT = 1
++def __P(protos): return protos
++
++def __STRING(x): return #x
++
++def __XSTRING(x): return __STRING(x)
++
++def __P(protos): return ()
++
++def __STRING(x): return x
++
++def __aligned(x): return __attribute__((__aligned__(x)))
++
++def __section(x): return __attribute__((__section__(x)))
++
++def __aligned(x): return __attribute__((__aligned__(x)))
++
++def __section(x): return __attribute__((__section__(x)))
++
++def __nonnull(x): return __attribute__((__nonnull__(x)))
++
++def __predict_true(exp): return __builtin_expect((exp), 1)
++
++def __predict_false(exp): return __builtin_expect((exp), 0)
++
++def __predict_true(exp): return (exp)
++
++def __predict_false(exp): return (exp)
++
++def __format_arg(fmtarg): return __attribute__((__format_arg__ (fmtarg)))
++
++def __FBSDID(s): return __IDSTRING(__CONCAT(__rcsid_,__LINE__),s)
++
++def __RCSID(s): return __IDSTRING(__CONCAT(__rcsid_,__LINE__),s)
++
++def __RCSID_SOURCE(s): return __IDSTRING(__CONCAT(__rcsid_source_,__LINE__),s)
++
++def __SCCSID(s): return __IDSTRING(__CONCAT(__sccsid_,__LINE__),s)
++
++def
Re: Problem building Openoffice 3.1.1 at -current
Hi Alexey, From: Alexey Shuvaev shuv...@physik.uni-wuerzburg.de Subject: Re: Problem building Openoffice 3.1.1 at -current Date: Sun, 04 Oct 2009 02:34:52 +0200 I hate OOO... me too... With the attached patch I was able to complete the build on amd64 9-CURRENT. Will charge 9-amd64-Ports and 9-i386-Ports tinderboxes to test in a clean environment. Testing on 8-RC is still welcome. Just drop patch-OOO_XXX_CURRENT into files/ and try to rebuild. many thanks for your patch. and it looks okay. BUT Please sign to SCA, otherwise we cannot upstream. http://porting.openoffice.org/freebsd/ If you would like to submit patches for OpenOffice.org, please fill out and submit SCA (or JCA or CA), (announcement). otherwise, we won't commit them, even for the FreeBSD ports cvs repo. If you want to learn more, please check the License FAQ. Here is a list of people who have signed the SCA, JCA and CA. thanks -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Problem building Openoffice 3.1.1 at -current
Hi folks! On Sat, Oct 3, 2009 at 7:34 PM, Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: On Mon, Sep 21, 2009 at 12:15:09PM -0700, Steve Kargl wrote: On Mon, Sep 21, 2009 at 02:39:44PM +0300, Andriy Gapon wrote: The above ln and cp were sufficient to complete my build. I haven't tested the resulting exectuables. Thanks, Andriy Rrrr The openoffice guys are trying to bundle every piece of code under the sun into their tarball in attempt to not depend upon system libraries... ... and are getting away from what they want to achieve (IMHO). OOO is as fragile as porcelain plate and still as complex to repair as nuclear u-boot. It sounds like OOO is designed to be compiled on a fresh system: I reformated a disk yesterday and the compilation of OOO just finished successfully. I loaded 8.0-RC1. As a matter of fact, I used the bundled modules - it takes longer but seems to be a bit more stable. My cent worth... ;-) Cheers Olivier ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
