419601 – dev-util/mingw64-runtime doesn't provide /usr/$CTARGET/mingw symlink

Bug 419601 - dev-util/mingw64-runtime doesn't provide /usr/$CTARGET/mingw symlink

Summary: dev-util/mingw64-runtime doesn't provide /usr/$CTARGET/mingw symlink

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Toolchain Maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-06-04 11:12 UTC by Alon Bar-Lev
Modified:	2012-06-06 22:18 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
cross-i686-w64-mingw32-info.log (cross-i686-w64-mingw32-info.log,14.93 KB, text/plain) 2012-06-04 11:13 UTC, Alon Bar-Lev	Details
cross-i686-w64-mingw32-gcc-stage1.log.xz (cross-i686-w64-mingw32-gcc-stage1.log.xz,26.04 KB, text/plain) 2012-06-04 11:13 UTC, Alon Bar-Lev	Details
gcc-config.logs.tar.xz (gcc-config.logs.tar.xz,39.08 KB, text/plain) 2012-06-04 11:14 UTC, Alon Bar-Lev	Details
cross-i686-w64-mingw32-mingw64-runtime-headers.log (cross-i686-w64-mingw32-mingw64-runtime-headers.log,39.83 KB, text/plain) 2012-06-04 11:15 UTC, Alon Bar-Lev	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alon Bar-Lev 2012-06-04 11:12:17 UTC

Hello,
Not sure this is crossdev issue or other component... I guess this is crossdev.
Used to work...

gcc looks for:
/usr/i686-w64-mingw32/mingw/include
while it should look in:
/usr/i686-w64-mingw32/i686-w64-mingw32/include/

Command used:
# USE="-hardened" crossdev -t i686-w64-mingw32

Please also consider to force the hardened USE in mingw targets automatically.

gcc error:
---
The directory that should contain system headers does not exist:
  /usr/i686-w64-mingw32/mingw/include
---

Comment 1 Alon Bar-Lev 2012-06-04 11:13:07 UTC

Created attachment 314159 [details]
cross-i686-w64-mingw32-info.log

Comment 2 Alon Bar-Lev 2012-06-04 11:13:46 UTC

Created attachment 314161 [details]
cross-i686-w64-mingw32-gcc-stage1.log.xz

Comment 3 Alon Bar-Lev 2012-06-04 11:14:19 UTC

Created attachment 314163 [details]
gcc-config.logs.tar.xz

Comment 4 Alon Bar-Lev 2012-06-04 11:15:00 UTC

Created attachment 314165 [details]
cross-i686-w64-mingw32-mingw64-runtime-headers.log

Comment 5 SpanKY gentoo-dev

2012-06-06 19:41:43 UTC

i don't think it's related to crossdev.  looks to me like gcc has always looked in "/mingw/include" rather than the $CTARGET.

gcc-4.1.2/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.2.4/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.3.0/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.3.1/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.3.2/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.3.3/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.3.4/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.3.5/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.4.0/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.4.1/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.4.2/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.4.3/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.4.4/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.4.5/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.4.6/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.4.7/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.5.0/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.5.0/gcc/config/i386/t-mingw-w64:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.5.1/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.5.1/gcc/config/i386/t-mingw-w64:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.5.2/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.5.2/gcc/config/i386/t-mingw-w64:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.5.3/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.5.3/gcc/config/i386/t-mingw-w64:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.0/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.0/gcc/config/i386/t-mingw-w32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.0/gcc/config/i386/t-mingw-w64:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.1/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.1/gcc/config/i386/t-mingw-w32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.1/gcc/config/i386/t-mingw-w64:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.2/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.2/gcc/config/i386/t-mingw-w32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.2/gcc/config/i386/t-mingw-w64:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.3/gcc/config/i386/t-mingw32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.3/gcc/config/i386/t-mingw-w32:NATIVE_SYSTEM_HEADER_DIR = /mingw/include
gcc-4.6.3/gcc/config/i386/t-mingw-w64:NATIVE_SYSTEM_HEADER_DIR = /mingw/include

Comment 6 Alon Bar-Lev 2012-06-06 19:50:05 UTC

This is strange... as the mingw64-runtime was not changed recently[1], I almost sure I merged in the past month.

Maybe toolchain.eclass[2]?


[1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-util/mingw64-runtime/
[2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/toolchain.eclass?r1=1.539&r2=1.540

Comment 7 SpanKY gentoo-dev

2012-06-06 19:58:36 UTC

should be all set now in the tree; thanks for the report!

Commit message: Always provide mingw symlink in sysroot for gcc
http://sources.gentoo.org/dev-util/mingw64-runtime/mingw64-runtime-2.0.1.ebuild?r1=1.1&r2=1.2

Comment 8 SpanKY gentoo-dev

2012-06-06 22:18:09 UTC

perhaps, but reading the gcc code, it seems like we should have always created this symlink ...