goffice uses removed pcre_info, causing gnumeric to crash

[saulsch@…]

Remark - I posted the following at GNOME Bugzilla (​https://bugzilla.gnome.org/show_bug.cgi?id=677755) -- they suggested I try to find the person maintaining the port. Here's what I wrote, slightly edited.

I am running Mac OS X 10.7.4. I just upgraded all of my packages through mac ports. Here is my version of gnumeric:

[~]$ port installed gnumeric
The following ports are currently installed:
  gnumeric @1.10.17_0+python27 (active)

Here is the crash I am seeing: I type

[~]$ gnumeric

and the program comes up in X11 (XQuartz 2.6.4 (xorg-server 1.10.6)). I type a few characters in any cell of the spreadsheet and hit return. The spreadsheet then freezes for a few moments, and then disappears. Here is the output on the terminal:

dyld: lazy symbol binding failed: Symbol not found: _pcre_info
  Referenced from: /opt/local/lib/libgoffice-0.8.8.dylib
  Expected in: flat namespace

dyld: Symbol not found: _pcre_info
  Referenced from: /opt/local/lib/libgoffice-0.8.8.dylib
  Expected in: flat namespace

Trace/BPT trap

I've tried installing older version of gnumeric. Either the problem persists or new problems show up. I've tried rolling back my copy of goffice - that doesn't seem to help either. I'm currently completely up to date and still seeing a consistent crash.

[ryandesign (Ryan Carsten Schmidt)]

The gnumeric port has no maintainer in MacPorts at this time.

_pcre_info... sounds like an incompatibility with the new pcre 8.30.

[saulsch@…]

I tried rolling back to 8.12_1:

[~]$ sudo port installed pcre
The following ports are currently installed:
  pcre @8.12_1 (active)
  pcre @8.30_1
[~]$ gnumeric
dyld: Library not loaded: /opt/local/lib/libpcre.1.dylib
  Referenced from: /opt/local/bin/gnumeric
  Reason: image not found
Trace/BPT trap

and I get a different error. Is there a particular version of pcre I should try?

[ryandesign (Ryan Carsten Schmidt)]

Please use WikiFormatting when writing in Trac.

You would have to rebuild gnumeric after downgrading to pcre 8.12.

sudo port -n upgrade --force gnumeric

And after I fix gnumeric to work with pcre 8.30, you'd have to rebuild it again after reactivating pcre 8.30.

[saulsch@…]

Well, then. I installed an older version of pcre via

svn co -r 84236 http://svn.macports.org/repository/macports/trunk/dports/devel/pcre

and macport removed, reinstalled goffice and gnumeric. Now I have

[~/pcre]$ sudo port installed pcre gnumeric goffice
The following ports are currently installed:
  gnumeric @1.10.17_0+python27 (active)
  goffice @0.8.17_2 (active)
  pcre @8.12_1 (active)
  pcre @8.30_1 

and gnumeric appears to be working. Yay! I'm not sure why this worked - I previously tried this exact collection of versions and it didn't work before? So perhaps the order of installation is also important? In any case, many thanks.

[saulsch@…]

Ah - just saw your comment. I activated pcre 8.12 but didn't rebuild goffice or gnumeric. That explains that. But doing "sudo port install" in the new (old) pcre directory had the same affect. Just to check - I can delete the extra pcre directory that I downloaded via svn, correct?

[ryandesign (Ryan Carsten Schmidt)]

Yes, you can delete the old pcre portfile directory if you like.

[saulsch@…]

Excellent. I've placed a link from the ticket at bugzilla (pointing to here) and tried to close that ticket. Thanks again for the help.

[ryandesign (Ryan Carsten Schmidt)]

I installed gnumeric and was unable to reproduce the problem. But perhaps gnumeric only uses pcre for example to read a configuration file, and since I haven't used gnumeric before, there wouldn't have been a configuration file.

In any case, I found ​a web page offering a fix for goffice 0.8 so it doesn't try to use the pcre_info function which was removed in pcre 8.30. I committed it in r94133. Wait 30 minutes, then "sudo port selfupdate". Let me know everything still works after re-activating pcre 8.30 and then upgrading goffice.

[jmroot (Joshua Root)]

You forgot to reference the patchfile in the portfile.

[ryandesign (Ryan Carsten Schmidt)]

I can see how that might not have the desired effect. Let's try again with r94159.

[saulsch@…]

Done - gnumeric still works. Thanks!