735878 – dev-games/aseprite-1.1.9: In file included from ../src/gfx/region.cpp:14: ../src/./gfx/region.h:54:38: error: no viable overloaded '='

Bug 735878 - dev-games/aseprite-1.1.9: In file included from ../src/gfx/region.cpp:14: ../src/./gfx/region.h:54:38: error: no viable overloaded '='

Summary: dev-games/aseprite-1.1.9: In file included from ../src/gfx/region.cpp:14: ../...

Status:	RESOLVED WONTFIX

Alias:	None

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

Importance:	Normal normal (vote)
Assignee:	Azamat H. Hackimov

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2020-08-04 06:39 UTC by Agostino Sarubbo
Modified:	2022-12-25 16:40 UTC (History)
CC List:	1 user (show)

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

Attachments
build.log (build.log,133.20 KB, text/plain) 2020-08-04 06:40 UTC, Agostino Sarubbo	Details
other.tar.bz2 (other.tar.bz2,5.28 KB, application/x-bzip-compressed-tar) 2020-08-04 06:40 UTC, Agostino Sarubbo	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 Agostino Sarubbo gentoo-dev

2020-08-04 06:39:54 UTC

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-games/aseprite-1.1.9 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 is strictly related to the LLD linker, please block bug 731004.

Comment 1 Agostino Sarubbo gentoo-dev

2020-08-04 06:40:00 UTC

Created attachment 652878 [details]
build.log

build log and emerge --info

Comment 2 Agostino Sarubbo gentoo-dev

2020-08-04 06:40:05 UTC

Created attachment 652880 [details]
other.tar.bz2

other logs

Comment 3 Azamat H. Hackimov 2022-12-25 16:40:11 UTC

1.1.9 removed from portage, 1.2.x branch changed internal structure, so I believe this issue is not actual. Please file new bug for 1.2.x if issue still persist.