First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 84874
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Linux Gnome Desktop Team <gnome@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Spider (RETIRED) <spider@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 84874 depends on: Show dependency tree
Bug 84874 blocks: 84701
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-03-11 09:44 0000 
Unfortunately so, testcase:
emerge -v \<nautilus-2.10 abiword;  emerge -u nautilus; ldd /usr/bin/AbiWord-2.2

Darkmere ~ # ldd /usr/bin/AbiWord-2.2
        linux-gate.so.1 =>  (0xffffe000)
        libnautilus.so.2 => not found
        libeel-2.so.2 => /usr/lib/libeel-2.so.2 (0xb7f45000)


abiword seems to link to nautilus private interfaces if it finds nautilus that it can use, which of course causes breakage because nautilus isn't ABI stable and isn't likely to ever be such.

Simple rebuild will disable the nautilus linking, however its obnoxious behaviour.

Is it worth it to release an abiword version that simply hardcodes the disable flag for nautilus?  (remove the -DHAVE_NAUTILUS=1 that configure adds )

------- Comment #1 From foser (RETIRED) 2005-03-21 16:04:28 0000 ------- 
Added an overriding define to 2.2.3 that sets HAVE_NAUTILUS=0 which i made x86
stable just now, hope it works as intended. This got fixed in versions >2.2.3
btw.
First Last Prev Next    No search results available      Search page      Enter new bug