Package Details: rtrlib 0.8.0-2

Git Clone URL: (read-only, click to copy)
Package Base: rtrlib
Description: RPKI-RTR client library
Upstream URL:
Licenses: MIT
Submitter: mroethke
Maintainer: mroethke
Last Packager: mroethke
Votes: 5
Popularity: 0.000000
First Submitted: 2017-02-02 15:08 (UTC)
Last Updated: 2024-06-18 13:01 (UTC)

Dependencies (3)

Sources (1)

Latest Comments

1 2 Next › Last »

mroethke commented on 2024-06-18 13:02 (UTC)


Frankkkkk commented on 2024-06-18 12:47 (UTC)

Ah, interesting, makes sense; I got my semantics wrong. Well, so if you could add armv7h and armv7l that'd be great :-) Thanks

mroethke commented on 2024-06-18 12:41 (UTC)


rtrlib is compiled from C to an architecture specific binary. If you compile this binary for ARM you cannot use it on x86 and vice versa. With a properly specified arch array pacman will prevent you from installing a package build for arm on x86. If I specify "any" pacman will not do that, because it thinks the package can be used on any architecture.

Frankkkkk commented on 2024-06-18 12:27 (UTC)

Can you explain the "containing compiled binaries" part please ? I don't really understand: isn't rtrlib compiled?

For the arch, at least armv7h. Thanks

mroethke commented on 2024-06-18 12:19 (UTC)

Any should never be specified on a package containing compiled binaries, because it would indicate that the build package can be installed on any architecture.

I would be happy to add desired architectures though.

Frankkkkk commented on 2024-06-18 10:26 (UTC)

Hi mroethke, could you change the architectures and specify any instead? The lib seems well built and works on armv7h and others, so I see no reason to restrict to the actual ones. Thanks!

mroethke commented on 2020-11-06 11:41 (UTC)


Undated4 commented on 2020-11-04 15:02 (UTC)

Please add aarch64 as a supported platform.

deconf commented on 2019-08-08 09:28 (UTC)

Thank you for your reminding, I am using --mflags --nocheck successfully installed the software

mroethke commented on 2019-08-08 09:04 (UTC)

Both tests need a connection to to work, the fact that they took almost exactly 20 seconds suggest that they timed out. You can build with --nocheck if that server is unreachable for some reason.