Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 645826 - Filezilla package not rebuilt when dependency package was rebuilt
Summary: Filezilla package not rebuilt when dependency package was rebuilt
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal
Assignee: Bernard Cafarelli
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-26 17:28 UTC by Davyd McColl
Modified: 2018-01-26 17:46 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Davyd McColl 2018-01-26 17:28:51 UTC
At some point, a package that filezilla (client) depends on must have been rebuilt, resulting in the following startup error from filezilla:

Reading locale option from /home/daf/.config/filezilla/filezilla.xml
Fatal Error: Mismatch between the program and library build versions detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8),
and your program used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8).
zsh: abort      filezilla

Rebuilding filezilla fixes the problem.


Reproducible: Always

Steps to Reproduce:
1. Install filezilla
2. Do system upgrades
3. Some time later, filezilla doesn't start
Actual Results:  
filezilla doesn't start correctly

Expected Results:  
filezilla should have been automatically rebuilt when it was necessary and started when I attempted to launch it

I'm note sure what the dependant package was (sorry). It just seems that there's some dependency which filezilla has which is not causing a rebuild after that dep is updated.
Comment 1 Mart Raudsepp gentoo-dev 2018-01-26 17:46:41 UTC
You seem to have failed to properly rebuild things using libstdc++ after some gcc upgrade, I believe there were news items about it. You've rebuilt wxGTK to use the new C++ ABI, but not filezilla, so you had wxGTK and filezilla C++ ABI differ, and wxGTK upstream has safeguards against it, which is the message you see.

However you've failed to include emerge --info, so not fully sure which C++ ABI change and which news item.

It is not possible to express C++ ABI in ebuilds (libstdc++ from gcc vs libcxx from llvm/clang stack, the ABI depending on the C++ compiler version used at buildtime, and so on), so there's nothing we can do here. Please complete your C++ ABI upgrade properly per relevant news items or otherwise.