Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fails to configure with Perl 5.38.0(-RC0) #170

Closed
akhuettel opened this issue Jun 6, 2023 · 1 comment · Fixed by #171
Closed

Fails to configure with Perl 5.38.0(-RC0) #170

akhuettel opened this issue Jun 6, 2023 · 1 comment · Fixed by #171

Comments

@akhuettel
Copy link
Contributor

https://github.com/Perl/perl5/blob/blead/pod/perldelta.pod#changes-to-existing-diagnostics
^ The "when" keyword moves from "experimental" to "deprecated in Perl 5.38.

This means it emits a warning, which triggers the use warnings FATAL => 'all'; at the start of BuildCommon.pm.

checking for valgrind... no
checking for Python 3.>=6 with Passlib... not found
configure: Disabling the "regen-ka-table" target, missing Python requirements.
checking whether all ucontext.h functions are available... yes
when is deprecated at /var/tmp/portage/sys-libs/libxcrypt-4.4.34/work/libxcrypt-4.4.34/build-aux/scripts/BuildCommon.pm line 522.
Compilation failed in require at /var/tmp/portage/sys-libs/libxcrypt-4.4.34/work/libxcrypt-4.4.34/build-aux/scripts/expand-selected-hashes line 28.
BEGIN failed--compilation aborted at /var/tmp/portage/sys-libs/libxcrypt-4.4.34/work/libxcrypt-4.4.34/build-aux/scripts/expand-selected-hashes line 28.
configure: error: bad value 'all' for --enable-hashes
@Leont Leont mentioned this issue Jun 6, 2023
Merged
@besser82
Copy link
Owner

besser82 commented Jun 6, 2023

Thank you for spotting this!

jbbjarnason added a commit to Skaginn3x/vcpkg-registry that referenced this issue Aug 8, 2023
@jbbjarnason
update libxcrypt
bf8f9dc 
besser82/libxcrypt#170
@jbbjarnason jbbjarnason mentioned this issue Aug 8, 2023
Merged
heiytor pushed a commit to shellhub-io/shellhub that referenced this issue Mar 25, 2024
chore(all): update go version to 1.21
173869f 
Due to the addition of the new `tests` directory, requiring Go version
`1.21`, we are updating the project's general Go version accordingly.
This update involves modifying all "go.mod" files and Dockerfiles.

The Dockerfiles utilizing `libxcrypto` encountered issues following the
update to `alpine` (please refer to
besser82/libxcrypt#170). This issue was
resolved in version `4.4.35`; however, a new bug surfaced as a
consequence of the upgrade. The newer version of the library
necessitates the `linux/mman.h` header, which is not provided by default
in alpine. To address this, we are now installing `linux-headers`.
gustavosbarreto pushed a commit to shellhub-io/shellhub that referenced this issue Mar 25, 2024
@gustavosbarreto
chore(all): update go version to 1.21
ae912e9 
Due to the addition of the new `tests` directory, requiring Go version
`1.21`, we are updating the project's general Go version accordingly.
This update involves modifying all "go.mod" files and Dockerfiles.

The Dockerfiles utilizing `libxcrypto` encountered issues following the
update to `alpine` (please refer to
besser82/libxcrypt#170). This issue was
resolved in version `4.4.35`; however, a new bug surfaced as a
consequence of the upgrade. The newer version of the library
necessitates the `linux/mman.h` header, which is not provided by default
in alpine. To address this, we are now installing `linux-headers`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make BuildCommon.pm compatible with latest perl Leont/libxcrypt
2 participants
@akhuettel @besser82