Bug 471714 – =app-emulation/wine-1.5.31 - configure:10894: error: libgphoto2 development files not found, digital cameras won't be supported. This is an error since --with-gphoto was requested.

• Status: RESOLVED CANTFIX
• Product: Gentoo Linux

[Description Toni Ballesta 2013-05-29 15:17:21 UTC]

Created attachment 349562 [details]
Build of wine-1.5.31

The package don't comes with development files for gphoto2 (and they USE don't masked). Compiles ok only with USE=-gphoto2. I recompile libgphoto2-2.4.14-r1 and is the same.

With wine-1.5.28, no problems.

[Comment 1 Jeroen Roovers (RETIRED) 2013-05-29 15:35:42 UTC]

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-emulation/wine-1.5.31/work/wine-1.5.31-x86/config.log

Please do!

[Comment 2 Toni Ballesta 2013-05-29 18:34:10 UTC]

Created attachment 349588 [details]
The requested log.

[Comment 3 Alexandre Rostovtsev (RETIRED) 2013-06-11 04:13:42 UTC]

(In reply to Antoni Ballesta from comment #2)
> Created attachment 349588 [details]

The following line

> PKG_CONFIG='i686-pc-linux-gnu-pkg-config'

suggests that the wrong version of pkg-config got detected (wine should have been using the normal systemwide /usr/bin/pkg-config executable), which may have led wine to use incorrect include paths. Please try with wine-1.6_rc1, which should detect pkg-config more reliably.

[Comment 4 Alexandre Rostovtsev (RETIRED) 2013-06-11 04:43:47 UTC]

Also, please check if doing

PKG_CONFIG=/usr/bin/pkg-config emerge -1 wine

fixes the problem

[Comment 5 Alexandre Rostovtsev (RETIRED) 2013-06-12 03:45:56 UTC]

I believe that like bug #472038, this was caused by wine attempting to use crossdev's i686-pc-linux-gnu-pkg-config instead of the normal system pkg-config tool. Fixed in cvs without a revision bump.

*** This bug has been marked as a duplicate of bug 472038 ***

[Comment 6 Fabio Rossi 2014-07-12 16:16:50 UTC]

I'm reopening this bug report because it seems the problem has just reappeared with >=wine-1.7.20. There have been some changes in the ebuild so probably this is the source of problems :-(

wine-1.7.19-r1 works fine

[Comment 7 Alexandre Rostovtsev (RETIRED) 2014-07-22 00:06:29 UTC]

(In reply to Fabio Rossi from comment #6)
> I'm reopening this bug report because it seems the problem has just
> reappeared with >=wine-1.7.20. There have been some changes in the ebuild so
> probably this is the source of problems :-(
> 
> wine-1.7.19-r1 works fine

Please attach your wine-*-x86/config.log and your emerge --info, make sure you are not using crossdev and that /usr/bin/i686-pc-linux-gnu-pkg-config is a true 32-bit executable belonging to dev-util/pkgconfig, not a wrapper script created by crossdev.

[Comment 8 Fabio Rossi 2014-07-22 17:10:29 UTC]

(In reply to Alexandre Rostovtsev from comment #7)
> (In reply to Fabio Rossi from comment #6)
> > I'm reopening this bug report because it seems the problem has just
> > reappeared with >=wine-1.7.20. There have been some changes in the ebuild so
> > probably this is the source of problems :-(
> > 
> > wine-1.7.19-r1 works fine
> 
> Please attach your wine-*-x86/config.log and your emerge --info, make sure
> you are not using crossdev and that /usr/bin/i686-pc-linux-gnu-pkg-config is
> a true 32-bit executable belonging to dev-util/pkgconfig, not a wrapper
> script created by crossdev.

Yes, I'm using crossdev and /usr/bin/i686-pc-linux-gnu-pkg-config points to the script created by crossdev

# file $(which i686-pc-linux-gnu-pkg-config )
/usr/bin/i686-pc-linux-gnu-pkg-config: symbolic link to `cross-pkg-config'

But this configuration works with <=wine-1.7.19-r1

I'm attaching the emerge log, the wine32 log and emerge --info.

[Comment 9 Fabio Rossi 2014-07-22 17:11:18 UTC]

Created attachment 381358 [details]
emerge-info.txt.gz

[Comment 10 Fabio Rossi 2014-07-22 17:11:56 UTC]

Created attachment 381360 [details]
wine-1.7.21-abi_x86_32.x86-config.log.gz

[Comment 11 Fabio Rossi 2014-07-22 17:13:42 UTC]

Created attachment 381362 [details]
wine-1.7.21:20140722-170410.log.gz

[Comment 12 Alexandre Rostovtsev (RETIRED) 2014-07-22 21:21:19 UTC]

(In reply to Fabio Rossi from comment #8)
> Yes, I'm using crossdev and /usr/bin/i686-pc-linux-gnu-pkg-config points to
> the script created by crossdev

I apologize, but this configuration is currently not supported. There are too many conflicts between i686-on-amd64 crossdev and new native multilib ebuilds like wine and libgphoto2, and lots of ways to get impossible-to-debug build failures.

Maybe a future crossdev version will play along better with multilib. But for now, if you really need i686 crossdev on amd64, please install it in a separate chroot.

[Comment 13 Alexandre Rostovtsev (RETIRED) 2014-07-22 21:26:25 UTC]

(In reply to Alexandre Rostovtsev from comment #12)
> for now, if you really need i686 crossdev on amd64, please install it in a
> separate chroot.

Or even simpler - move all the wrapper scripts from /usr/bin into a separate directory (like /usr/local/crossdev/bin) and add it to your PATH only when crossdev is needed, not when installing normal ebuilds.

[Comment 14 Fabio Rossi 2014-07-23 07:48:22 UTC]

It seems there is a well known conflict between crossdev and multilib, anyway it seems that the wrapper script relocation you suggest is not an approved solution for other gentoo devs (see bug #504824)

As a reference I'll put here a link to a gentoo-dev mailing list thread about the current discussion still going on: http://marc.info/?l=gentoo-dev&m=139463917910222&w=2