602714 – app-misc/datefudge doesn’t compile with musl

Bug 602714 - app-misc/datefudge doesn’t compile with musl

Summary: app-misc/datefudge doesn’t compile with musl

Status:	RESOLVED UPSTREAM

Alias:	None

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

Importance:	Normal normal
Assignee:	No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it

URL:
Whiteboard:
Keywords:	UPSTREAM

Depends on:
Blocks:	musl-porting
	Show dependency tree

Reported:	2016-12-14 22:57 UTC by Haelwenn (lanodan) Monnier
Modified:	2018-07-12 13:23 UTC (History)
CC List:	1 user (show)

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

Attachments
amd64-musl-hardened build.log (build.log,2.21 KB, text/x-log) 2016-12-14 22:57 UTC, Haelwenn (lanodan) Monnier	Details
Untested patch (patch,1.05 KB, patch) 2016-12-14 23:59 UTC, Felix Janda	Details \| Diff
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 Haelwenn (lanodan) Monnier 2016-12-14 22:57:56 UTC

Created attachment 456254 [details]
amd64-musl-hardened build.log

Reproduced on:
* armv7-musl
* amd64-musl-hardened

Comment 1 Haelwenn (lanodan) Monnier 2016-12-14 23:00:28 UTC

Additionnal notes:
* doesn’t reproduce on amd64-uclibc-hardened and amd64-hardened
* the bug seems to be upstream (reproducable in the git repo)

Comment 2 Felix Janda 2016-12-14 23:59:50 UTC

Created attachment 456260 [details, diff]
Untested patch

The patch should fix compilation with musl libc but might break glibc
and/or uclibc. It would be very nice if you could test it on all these
targets.

Comment 3 Haelwenn (lanodan) Monnier 2016-12-15 00:14:48 UTC

make test doesn’t work (uses dpkg-parsechangelog) but it compiles successfully on :
* amd64-glibc-hardened
* amd64-musl-hardened
* amd64-uclibc-hardened

Comment 4 Pacho Ramos gentoo-dev

2018-06-20 14:51:32 UTC

I would try to send this to upstream to get it solved in future releases (and to check if they really agree on fixing this in this way)