Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 527980 - cross-i686-w64-mingw32/gcc-4.8.3 - /usr/i686-w64-mingw32/lib/libmingw32.a(lib32_libmingw32_a-pseudo-reloc.o):pseudo-reloc.c:(.text+0x2aa): undefined reference to `__stack_chk_guard'
Summary: cross-i686-w64-mingw32/gcc-4.8.3 - /usr/i686-w64-mingw32/lib/libmingw32.a(lib...
Status: RESOLVED DUPLICATE of bug 513706
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-02 09:29 UTC by Luke-Jr
Modified: 2015-05-05 06:48 UTC (History)
0 users

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


Attachments
build.log.xz (build.log.xz,36.75 KB, application/x-xz)
2014-11-02 09:29 UTC, Luke-Jr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luke-Jr 2014-11-02 09:29:43 UTC
Created attachment 388314 [details]
build.log.xz

gcc-4.8.3 rebuilds were triggered by a new 'sanitize' USE flag. However, the ebuild does not compile for MinGW targets with that USE flag enabled (at least 32-bit - 64-bit doesn't get this far due to bug #527976). Following up after #525942, the build is still broken. I suggest USE=sanitize be masked for Windows profiles.
Comment 1 Luke-Jr 2014-11-02 09:34:57 UTC
Sorry, clicked submit too quick - this issue exists with OR without USE=sanitise
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2014-11-02 18:52:51 UTC

*** This bug has been marked as a duplicate of bug 525910 ***
Comment 3 Luke-Jr 2014-11-03 05:18:41 UTC
(In reply to Jeroen Roovers from comment #2)
> *** This bug has been marked as a duplicate of bug 525910 ***

Sorry again for the confusion. As mentioned in comment 1, this issue is not related to USE=sanitize, and still occurs without it.
Comment 4 SpanKY gentoo-dev 2015-05-05 06:48:22 UTC

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