Bug 627046 – >sys-apps/systemd-233 needs >=dev-util/gperf-3.1

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Ulenrich 2017-08-04 12:54:17 UTC]

regarding https://github.com/systemd/systemd/blob/master/NEWS 
CHANGES WITH 233:
        * This version requires at least gperf 3.1 for building, 3.0 is not
          sufficient.
---
Shouldn't dependency on gperf be versioned?

And what is troubling: 
systemd-233 is stable 
gperf-3.1 is unstable

[Comment 1 Mike Gilbert 2017-08-04 18:13:25 UTC]

Do you experience any build failure with gperf-3.0?

[Comment 2 Mike Gilbert 2017-08-04 18:16:51 UTC]

I'm fairly certain the NEWS file is wrong.

[Comment 3 Ulenrich 2017-08-05 21:06:51 UTC]

Not personally experienced a build failure, because I have Gentoo~unstable.
This is odd, never have seen such an announced requirement of version, when unnecessary ...

... Perhaps upstream systemd developers think of an enhanced security feature that gperf-3.1 provides?

[Comment 4 Ulenrich 2017-08-05 21:25:48 UTC]

gperf-3.1 has nine years developement since gperf-3.0.4
---gperf-3.1 NEWS
* The 'len' parameter of the hash function and of the lookup function is now
  of type 'size_t' instead of 'unsigned int'. This makes it safe to call these
  functions with strings of length > 4 GB, on 64-bit machines.
---
What about systemd dumps, or elsewhere: Is there needed any hash with >4GB
?

[Comment 5 Mike Gilbert 2017-08-06 13:06:05 UTC]

(In reply to Ulenrich from comment #4)

gperf is only used for strings that are defined at build time, none of which are more than a 100 bytes long.

Anyway, upstream merged my revert of the NEWS change, so this was likely a mistake on their part.

[Comment 6 Pacho Ramos 2017-08-09 13:11:18 UTC]

As a side note, I am using latest systemd with stable gperf-3.0 without issues