LinuxQuestions.org - [SOLVED] SBo wine-nine issue with pkconfig 14.2 64-bit multilib

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

- - SBo wine-nine issue with pkconfig 14.2 64-bit multilib (https://www.linuxquestions.org/questions/slackware-14/sbo-wine-nine-issue-with-pkconfig-14-2-64-bit-multilib-4175680456/)

SBo wine-nine issue with pkconfig 14.2 64-bit multilib

Hello, I am trying to install wine-nine-standalone from SBo, however I get an error:

Code:

Trying pkg-config binary i586-slackware-linux-gnu-pkg-config for machine MachineChoice.HOST at [None]

Did not find pkg-config by name 'i586-slackware-linux-gnu-pkg-config'

Found Pkg-config: NO

Pkg-config binary for machine MachineChoice.HOST not found. Giving up.

CMake binary for MachineChoice.HOST is not cached

None of  are defined in the environment, not changing global flags.

CMake binary missing from cross or native file, or env var undefined.

Found CMake: NO

No CMake binary for machine MachineChoice.HOST not found. Giving up.

Run-time dependency d3d found: NO (tried pkgconfig and cmake)

Message: trying alternative name for d3d...

Pkg-config binary for MachineChoice.HOST is cached as not found.

Pkg-config binary for machine MachineChoice.HOST not found. Giving up.

CMake binary for MachineChoice.HOST is cached as not found

No CMake binary for machine MachineChoice.HOST not found. Giving up.

Run-time dependency d3dadapter9 found: NO 



meson.build:76:2: ERROR: Pkg-config binary for machine MachineChoice.HOST not found. Giving up.

Current configuration:
1. Installed pkgconf from SBo and pkg-config was removed.
2. Just before posting, I installed meson-0.54.1-x86_64-1alien from meson-0.52.1-x86_64-1_SBo to see if this would help.

Should I be creating a symbolic link to i586-slackware-linux-gnu-pkg-config from pkgconf? Or does pkgconf need to be turned to a 32-bit library?

cat /var/log/sbopkg/sbopkg-build-log : wine-nine.txt
cat /tmp/SBo/wine-nine-standalone-0.5/build32/meson-logs/meson-log.txt : meson-log.txt

Thank you in advance.

Quote:

Originally Posted by ernie young (Post 6156143)

Hello, I am trying to install wine-nine-standalone from SBo, however I get an error:

Code:

Trying pkg-config binary i586-slackware-linux-gnu-pkg-config for machine MachineChoice.HOST at [None]

Did not find pkg-config by name 'i586-slackware-linux-gnu-pkg-config'

Found Pkg-config: NO

Pkg-config binary for machine MachineChoice.HOST not found. Giving up.

CMake binary for MachineChoice.HOST is not cached

None of  are defined in the environment, not changing global flags.

CMake binary missing from cross or native file, or env var undefined.

Found CMake: NO

No CMake binary for machine MachineChoice.HOST not found. Giving up.

Run-time dependency d3d found: NO (tried pkgconfig and cmake)

Message: trying alternative name for d3d...

Pkg-config binary for MachineChoice.HOST is cached as not found.

Pkg-config binary for machine MachineChoice.HOST not found. Giving up.

CMake binary for MachineChoice.HOST is cached as not found

No CMake binary for machine MachineChoice.HOST not found. Giving up.

Run-time dependency d3dadapter9 found: NO 



meson.build:76:2: ERROR: Pkg-config binary for machine MachineChoice.HOST not found. Giving up.

Current configuration:
1. Installed pkgconf from SBo and pkg-config was removed.
2. Just before posting, I installed meson-0.54.1-x86_64-1alien from meson-0.52.1-x86_64-1_SBo to see if this would help.

Should I be creating a symbolic link to i586-slackware-linux-gnu-pkg-config from pkgconf? Or does pkgconf need to be turned to a 32-bit library?

cat /var/log/sbopkg/sbopkg-build-log : https://termbin.com/l9io
cat /tmp/SBo/wine-nine-standalone-0.5/build32/meson-logs/meson-log.txt : https://termbin.com/shxw9

Thank you in advance.

I think someone asked the same thing on irc a few days ago and the maintainer of wine-nine-standalone suggested him to substitute the installed pkg-config with pkgconf to let wine-nine-standalone to build: I suggest you to get in touch with him for more details.

Thanks for the help Ponce. That could have been me that received help some weeks ago. I did remove pkg-config (default) from my system and installed pkgconf from SBo, however I am getting the error posted. The person helping me, orbea, could not find a solution, hence why I am posting here. If I find a solution, I shall post it here too.

Can you paste the output of this command?

Code:

which i586-slackware-linux-gnu-pkg-config

Please don't use termbin for forum posts, those links are temporary.

Quote:

$ which i586-slackware-linux-gnu-pkg-config
which: no i586-slackware-linux-gnu-pkg-config in (/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/java/bin:/usr/lib64/java/jre/bin:/usr/lib64/qt/bin:/usr/lib64/qt5/bin:/usr/share/texmf/bin:/sbin)

Thanks for that tip!

How about this command?

Code:

ls /var/log/packages/pkgconf*

Output:

Quote:

$ ls /var/log/packages/pkgconf*
/var/log/packages/pkgconf-1.7.3-x86_64-1_SBo

And this command?

Code:

cat /var/log/packages/pkgconf-1.7.3-x86_64-1_SBo

I am attaching it, is that fine?

That works.

How about this command?

Code:

cat /usr/bin/i586-slackware-linux-gnu-pkg-config

I just saw that it's not there

Quote:

$ ls /usr/bin/ | grep i586*
i586-slackware-linux-gnu-pkg-config.bak

Quote:

$ stat /usr/bin/i586-slackware-linux-gnu-pkg-config
stat: cannot stat '/usr/bin/i586-slackware-linux-gnu-pkg-config': No such file or directory

Quote:

$ cat /usr/bin/i586-slackware-linux-gnu-pkg-config
cat: /usr/bin/i586-slackware-linux-gnu-pkg-config: No such file or directory

I deleted pkgconf and installed it again from SBo and now:

Quote:

ls /usr/bin/ | grep i586*
i586-slackware-linux-gnu-pkg-config
i586-slackware-linux-gnu-pkg-config.bak

I also tried re-installing wine-nine again, attached.

You can get rid of /usr/bin/i586-slackware-linux-gnu-pkg-config.bak, if I recall that was from the last time we tried to solve this in irc.

Can you try the wine-nine-standalone build again? If it fails please attach the log to the thread.

In post #12 I did the re-install. I tried again but it continues to fail as can be seen in the attachment.

Yes, can you try building wine-nine-standalone again? I think it will have a different error at least.