User forums > Help
Installing 17.12 on Linux Mint --wxWidgets problem
oBFusCATed:
--- Quote from: rjmoses on January 15, 2019, 11:48:49 am ---This process did allow CB 17.12 to run under Linux Mint 18.3 but as I suspected, I had to remove and reinstall filezilla and audacity.
--- End quote ---
If you've used the wrong prefix then you've messed up your system. But this is not the default behaviour. The other way you can mess this up is you've built filezilla with another version of wxgtk. But then the fault is all yours.
--- Quote from: rjmoses on January 15, 2019, 11:48:49 am ---IMO, this is not an acceptable process!
--- End quote ---
Yes, this is why people use packages and learning how to make packages yourself is a good idea.
--- Quote from: rjmoses on January 15, 2019, 11:48:49 am ---Someone with less experience would probably not completed this task and would have been left with a bad taste about CB and Linux in general.
--- End quote ---
Then they'll learn to use packages or switch to either windows/osx/chromeos/whatever. It is not the end of the world anyway. Building code manually requires a lot of knowledge and persistence to always do the correct non-messing up thing and it is not for novices. I guess this is why things like docker and other container managers are popular now. They make it hard for you to mess systems up.
--- Quote from: rjmoses on January 15, 2019, 11:48:49 am ---Further, I believe compiler dependency in widgets takes version control too far. This is probably something widgets needs to take care of. (I did see one post where the widgets developers were considering removing that in a future release, but I don't know if it has been done yet.)
--- End quote ---
I don't have am idea what you're talking about.
sodev:
--- Quote from: rjmoses on January 15, 2019, 11:48:49 am ---This process did allow CB 17.12 to run under Linux Mint 18.3 but as I suspected, I had to remove and reinstall filezilla and audacity.
--- End quote ---
I don't know what you did, but this should not be necessary and is a sign of that you screwed your system. Your system libraries all reside under
--- Code: ---/usr
--- End code ---
while so far as i have seen all selfbuild source packages by default go into
--- Code: ---/usr/local
--- End code ---
. wxWidgets libraries use versioned filenames so your system applications won't pick up your local ones unless the version is identical but then your local ones should be binary compatible (but might miss some components you didn't build).
Anyway, you could save yourself from this if you simply would have build against your system library!
--- Quote from: rjmoses on January 15, 2019, 11:48:49 am ---IMO, this is not an acceptable process! While I accomplished my result, I spent over 20 hours digging into the problem and researching how to overcome it. Someone with less experience would probably not completed this task and would have been left with a bad taste about CB and Linux in general.
--- End quote ---
Linux != Windows
[MyOpinionStart]
Although there are nice package managers and stuff around, if you are using Linux you should know what a compiler is and how to compile stuff and especially what a shell ist, this is just not your point-and-click OS
[MyOpinionEnd]
--- Quote from: rjmoses on January 15, 2019, 11:48:49 am ---Further, I believe compiler dependency in widgets takes version control too far.
--- End quote ---
This is actually a very good thing, without this instead of getting this error message you would get obscure, random runtime crashes which are extremely hard to debug. Even considerung the above point ;D.
rjmoses:
--- Quote from: BlueHazzard on January 15, 2019, 06:46:36 pm ---i know for you this topic is closed. but me would interest why you used 3.1.2 and not the system default library, so you do not have to uninstall filezilla and audacity...
--- End quote ---
Very good question!
It is the current release and my thought was that I would not be chasing problems that may have been already resolved. By building from the current versions of both CB and wsWidgets, I believed I would be working with the code that the developers are confident in. (I am assuming that the CB developers are working the 3.1.2.)
For whatever reason, the Synpatics Package Manager under Mint 18.3 only supported CB 13.12 and wxWidgets 3.0.2 which is what got me into trouble in the first place.
So, I elected to do complete removals and re-installs on those audacity and filezilla to make sure I had a clean widgets base to work from and avoid potential package conflicts.
Here are links to posts that alluded to the ABI check going away:
https://bugzilla.redhat.com/show_bug.cgi?id=1200611
https://bugzilla.redhat.com/show_bug.cgi?id=1318171
Navigation
[0] Message Index
[*] Previous page
Go to full version