Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 734344 - app-office/scribus-1.5.7 fails to compile: path.h:260:11: error: no viable overloaded '='
Summary: app-office/scribus-1.5.7 fails to compile: path.h:260:11: error: no viable ov...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Miroslav Šulc
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-29 05:57 UTC by Agostino Sarubbo
Modified: 2023-02-20 11:05 UTC (History)
1 user (show)

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


Attachments
build.log (build.log,211.87 KB, text/plain)
2020-07-29 05:58 UTC, Agostino Sarubbo
Details
other.tar.bz2 (other.tar.bz2,4.41 KB, application/x-bzip-compressed-tar)
2020-07-29 05:58 UTC, Agostino Sarubbo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2020-07-29 05:57:58 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: app-office/scribus fails to compile.
Discovered on: amd64 (internal ref: tinderbox)

NOTE:
This machine uses a clang/LLVM toolchain.
If you think that this issue is strictly related to clang/LLVM please block bug 408963. If you think that this issue isstrictly related to the LLD linker, please block bug 731004.
Comment 1 Agostino Sarubbo gentoo-dev 2020-07-29 05:58:04 UTC
Created attachment 651352 [details]
build.log

build log and emerge --info
Comment 2 Agostino Sarubbo gentoo-dev 2020-07-29 05:58:07 UTC
Created attachment 651354 [details]
other.tar.bz2

other logs
Comment 3 Agostino Sarubbo gentoo-dev 2021-12-14 08:50:59 UTC
tinderbox has reproduced this issue with version 1.5.7 - Updating summary.
Comment 4 Andreas Sturmlechner gentoo-dev 2023-02-20 10:59:35 UTC
You're not updating this bug anymore so can we assume it is fixed?
Comment 5 Agostino Sarubbo gentoo-dev 2023-02-20 11:05:40 UTC
(In reply to Andreas Sturmlechner from comment #4)
> You're not updating this bug anymore so can we assume it is fixed?

yes, let's say it is fixed.