Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 776595 - ERROR: dev-libs/boost-1.75.0::gentoo failed (compile phase)
Summary: ERROR: dev-libs/boost-1.75.0::gentoo failed (compile phase)
Status: RESOLVED DUPLICATE of bug 724314
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal critical (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-16 02:40 UTC by Austin Kilgore
Modified: 2021-03-16 14:46 UTC (History)
1 user (show)

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


Attachments
build.log and emerge --info (build-log-and-emerge-info.tar.gz,9.07 KB, application/gzip)
2021-03-16 02:40 UTC, Austin Kilgore
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Austin Kilgore 2021-03-16 02:40:19 UTC
Created attachment 691644 [details]
build.log and emerge --info

Tried updating and boost failed without a clear reason.
Comment 1 Marco Scardovi (scardracs) 2021-03-16 14:42:12 UTC
(In reply to Austin Kilgore from comment #0)
> Created attachment 691644 [details]
> build.log and emerge --info
> 
> Tried updating and boost failed without a clear reason.

If you check line 253 there is a stack smashing, which is a protection added in gcc for buffer overflow. More info about stack smashing here: https://stackoverflow.com/questions/1345670/stack-smashing-detected/50690687
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-03-16 14:44:14 UTC

*** This bug has been marked as a duplicate of bug 724314 ***
Comment 3 Marco Scardovi (scardracs) 2021-03-16 14:46:19 UTC
(In reply to Marco Scardovi from comment #1)
> (In reply to Austin Kilgore from comment #0)
> > Created attachment 691644 [details]
> > build.log and emerge --info
> > 
> > Tried updating and boost failed without a clear reason.
> 
> If you check line 253 there is a stack smashing, which is a protection added
> in gcc for buffer overflow. More info about stack smashing here:
> https://stackoverflow.com/questions/1345670/stack-smashing-detected/50690687

Obviously I mean line 253 of build.log