Re: openoffice is compiling again!...but won't run.
On Fri, Jul 12, 2002 at 10:02:35AM +0200, Martin Blapp wrote: sjlj and dwarf2 work. But the problem with CURRENT is that this patch seems to be needed. (Patch from Alexander Kabaev) This patch is wrong. I committed a correct one from Alxander. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: openoffice is compiling again!...but won't run.
hi, there! On Fri, Jul 12, 2002 at 01:30:47AM +0200, Martin Blapp wrote: Make sure you use the ports gcc31 for compiling. The c++ from CURRENT has broken exception handling. In the next few days a patch will be committed to address this. btw does it still use -fsjlj method for exception handling? /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: openoffice is compiling again!...but won't run.
Hi, btw does it still use -fsjlj method for exception handling? sjlj and dwarf2 work. But the problem with CURRENT is that this patch seems to be needed. (Patch from Alexander Kabaev) Index: config/i386/freebsd.h === RCS file: /usr/ncvs/src/contrib/gcc/config/i386/freebsd.h,v retrieving revision 1.56 diff -u -r1.56 freebsd.h --- config/i386/freebsd.h 21 Jun 2002 22:53:03 - 1.56 +++ config/i386/freebsd.h 26 Jun 2002 20:55:44 - @@ -385,11 +385,9 @@ #define DBX_CHECK_FUNCTION_FIRST TARGET_ELF #undef DBX_REGISTER_NUMBER -#define DBX_REGISTER_NUMBER(n) (TARGET_64BIT ? dbx64_register_map[n] \ - : (write_symbols == DWARF2_DEBUG\ - || write_symbols == DWARF_DEBUG) \ - ? svr4_dbx_register_map[(n)] \ - : dbx_register_map[(n)]) + +#define DBX_REGISTER_NUMBER(n) \ + (TARGET_64BIT ? dbx64_register_map[n] :svr4_dbx_register_map[(n)]) /* tag end of file in elf mode */ #undef DBX_OUTPUT_MAIN_SOURCE_FILE_END Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: openoffice is compiling again!...but won't run.
On 11 Jul, walt wrote: I just finished compiling and installing openoffice on yesterday's -current, thanks to the stat.h patch from Bruce. It even runs properly for me if I access my previously setup home directory NFS mounted from a stable box. Also, it successfully reads a Word document that caused the version compiled on -stable to core dump. Unfortunately, the 'setup' program segfaults just like it did two months ago. This was fixed in -stable with Matt's patch for rtld-elf, but that patch won't apply in -current. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: openoffice is compiling again!...but won't run.
:On 11 Jul, walt wrote: : I just finished compiling and installing openoffice on yesterday's : -current, thanks to the stat.h patch from Bruce. : :It even runs properly for me if I access my previously setup home :directory NFS mounted from a stable box. Also, it successfully reads a :Word document that caused the version compiled on -stable to core dump. : : Unfortunately, the 'setup' program segfaults just like it did : two months ago. This was fixed in -stable with Matt's patch for : rtld-elf, but that patch won't apply in -current. I had committed the alloca()-mmap() change to both -current and -stable. Is that the patch you were talking about? -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: openoffice is compiling again!...but won't run.
Don Lewis wrote: On 11 Jul, walt wrote: I just finished compiling and installing openoffice on yesterday's -current, thanks to the stat.h patch from Bruce.[but it won't run] It even runs properly for me if I access my previously setup home directory NFS mounted from a stable box. Also, it successfully reads a Word document that caused the version compiled on -stable to core dump. That's great news. My compile run did quit in the middle twice for various reasons, but it did in -stable also and that runs fine. I'll try another compile again tonight. Just like two months ago the binaries for -current are smaller that for -stable, which bothers me. How does this compare to yours? -CURRENT: -rwxr-xr-x 1 root wheel234948 Jul 11 07:00 setup.bin* -rwxr-xr-x 1 root wheel281517 Jul 11 07:00 soffice.bin* -rwxr-xr-x 1 root wheel 15392 Jul 11 07:00 spadmin.bin* -STABLE: -rwxr-xr-x 1 root wheel268548 Jun 22 10:43 setup.bin* -rwxr-xr-x 1 root wheel401270 Jun 22 10:44 soffice.bin* -rwxr-xr-x 1 root wheel 20014 Jun 22 10:43 spadmin.bin* To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: openoffice is compiling again!...but won't run.
Hi, Make sure you use the ports gcc31 for compiling. The c++ from CURRENT has broken exception handling. In the next few days a patch will be committed to address this. And we have a special mailinglist for openoffice now :-) Please mail to [EMAIL PROTECTED] You could also get one of the packages compiled with gcc31 on STABLE, which run wonderful on CURRENT with compat libs ... http://www.imp.ch/openoffice Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
