LinuxQuestions.org - [SOLVED] Installation of mysql-workbench asking some weird packages.

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Installation of mysql-workbench asking some weird packages. (https://www.linuxquestions.org/questions/slackware-14/installation-of-mysql-workbench-asking-some-weird-packages-4175447196/)

Hmmm.

I read online and found that above error is caused by package gcc-c++ , which i couldn't find for Slackware. Then i moved to gcc-g++ and reinstalled v4.7.2 . Now i realized something's wrong, so removed both versions and did a clean installation of v4.7.2. On running slackpkg upgrade-all i found that the mirror i had selected had only version 4.7.1. So i uninstalled v4.7.2 and did a clean installation of version 4.7.1.

In the middle of this mayhem installation of mysql-workbench started giving /lib/cpp error.

But now its gone, and in farewell, gifted me a new kind of error which is described below!

Code:

In file included from /usr/include/boost/signals2/detail/foreign_ptr.hpp:18:0,

                from /usr/include/boost/signals2/slot_base.hpp:18,

                from /usr/include/boost/signals2/detail/tracked_objects_visitor.hpp:18,

                from /usr/include/boost/signals2/slot.hpp:22,

                from /usr/include/boost/signals2/connection.hpp:23,

                from base/trackable.h:24,

                from base/ui_form.h:29,

                from ui_form.cpp:23:

/usr/include/boost/smart_ptr/bad_weak_ptr.hpp:39:7: error: redefinition of 'class boost::bad_weak_ptr'

In file included from /usr/include/boost/detail/shared_count.hpp:28:0,

                from /usr/include/boost/shared_ptr.hpp:32,

                from base/trackable.h:23,

                from base/ui_form.h:29,

                from ui_form.cpp:23:

/usr/include/boost/detail/bad_weak_ptr.hpp:39:7: error: previous definition of 'class boost::bad_weak_ptr'

make[3]: *** [ui_form.lo] Error 1

make[3]: Leaving directory `/tmp/build/mysql-workbench-gpl-5.2.45-src/library/base'

make[2]: *** [all-recursive] Error 1

make[2]: Leaving directory `/tmp/build/mysql-workbench-gpl-5.2.45-src/library'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/tmp/build/mysql-workbench-gpl-5.2.45-src'

make: *** [all] Error 2

That's it. What done is done. Going for a clean reinstall NOW!

Thank you for having me!

I really don't know why you did all that.
<rant>Don't follow (blindly) any advise on line especially if they are not intended for your version of your distribution: stay with us or leave for good.</rant>
Of course the error can't be caused by a package which is not part of Slackware (and don't be fooled by packages's names anyway: content of packages bearing the same name are not the same across distributions, and the same library can be found in packages named differently across distributions).
Besides, why install gcc-g++ v-4.7.2 as Slackware includes version v-4.7-1, why???

Now my best advise would be to clean your system before doing anything else:

Code:

slackpkg update

slackpkg upgrade-all

slackpkg clean-system # Keep only the packages you are sure you should keep.

EDIT I didn't see your last post before posting. Anyway, don't worry: making mistakes (and understanding why they are mistakes) is still the best way to learn. Take care.

Thanks Didier,

Actually i had upgraded my slack to slack current. And then maybe messing with deb packages using deb2tgx causes the problem. After reinstalling slack, i found that most people find slack current as much stable as slack stable. So i decided to upgrade to current.

Is there any difference between installing mysql-workbench in slack 14 and slack current? Should i upgrade to current? Would i able to install mysql-workbench in slack current?

Sorry for bugging again on dead thread.

Slackware-current public exposure's purpose is to get a chance to be tested as thoroughly as possible before it becomes the next stable release.

But for a regular user there is really no advantage running -current - there are inconveniences instead:
(1) it may become instable at some point of time and is harder to keep up to date. It may happen that you even have to reinstall from scratch.
(2) it makes harder to install third party packages. For instance http://slackbuilds.org does not provide SlackBuilds for -current.

You won't get any advantage, nor see any difference, in running mysql-workbench in -current. Its installation will only be more difficult.

So my advise is: stay with Slackware-14.0.

Also consider that people running -current are supposed to be able to solve themselves the problems which can occur using it. So if you want to try, at least wait till you be a little more experienced.

Oh, and as already said, do not try to install packages not intended for Slackware-14 - in particular do not try to install .deb packages.

PS You will find on slackbuilds.org a few SlackBuilds which re-package .deb packages. You may safely use these SlackBuilds as they are carefully reviewed, but do not use the .debs in any other way.

HTH,

Thanks Didier for such a great explanation.

There's no problem building mysql-workbench on -current
in fact, i tested both on -Current and -Stable on my machine for my mysql-workbench in my SlackHacks repository

@Willy: that's good, but out of curiosity why the need of keeping the (almost) same stuff on two different repositories? in other words, why not simply push the changes you made on SlackHacks to slackbuilds.org?

@unkn(o)wn: that doesn't mean you should go for -current. In fact what Willy said merely confirm that in this case at least, you wouldn't see any difference in using -14 or -current ;)

it's because i'm not the current maintainer of mysql-workbench in SBo, so it's not my privileges to submit changes to SBo, except when two things happened:
1. The current maintainer stepped down and i took maintainership
2. New Slackware version is coming and the admins stopped submission to test all the scripts to make sure it works in next slackware release

The only reason why i'm testing in two environments is because SBo requires that a package is built on stable releases, while my slackhacks is intended for my own private testing on packages for current and hopefully when new slackware version comes out, i don't have to test again and just submitted my packages to SBo :)

I see, thanks for your explanation, Willy. :cool: