User forums > Using Code::Blocks

[SOLVED] 'AM_OPTIONS_WXCONFIG' not found in library

<< < (2/5) > >>

hidefromkgb:
…guys?

sodev:
If you mess up your system it is your job to clean it up.

You have at least two wxWidgets versions installed, forcefully installed a selfmade wx-config package and yet Automake is looking for a third one which apparently is not installed. If you use multiple wxWidgets versions installation order is important because it determines which one gets used by default. Your selfmade package can make the situation worse if it doesn't follow the style of your distro. Maybe you are also reusing the source tree which has some cached values that mess up things even further.

If you are lucky it is enough to pass the wx-config of the wxWidgets version you want to use to the configure script (it has a nice help switch that shows you all options it supports). If your are not so lucky you need to get rid at least of all dev-packages of wxWidgets and your selfmade package and reinstall only the dev-package of the wxWidgets version you want to use. And if that doesn't help there is always mv / /dev/null.

hidefromkgb:

--- Quote from: sodev on September 25, 2019, 01:33:01 am ---If you mess up your system it is your job to clean it up.

--- End quote ---

* What gave you the idea I messed my system up? Everything I install, I install via the standard package manager, converting packages to its native format if needed.
* Do you actually have to be so toxic in response to a simple question of what went wrong with the build?

stahta01:
What does the command below return?

--- Code: ---wx-config --list

--- End code ---


Edit: What version of Code::Blocks are you trying to build?
Edit2: What exactly are the commands you are using?
Edit3: What does the command below return?

--- Code: ---/usr/bin/wx-config-gtk3 --list

--- End code ---

Tim S.

oBFusCATed:
My guess is either that the wxwin.m4 file is not found or you have something in the toolchain (m4, autotools, automake) which is too new and we don't support it... A third options is that you have something cached from a previous failed run.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version