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.

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

m4 requires a patch to update it to the newest glibc #285

Closed
maenpaa24 opened this issue Apr 16, 2019 · 1 comment
Closed

m4 requires a patch to update it to the newest glibc #285

maenpaa24 opened this issue Apr 16, 2019 · 1 comment

Comments

@maenpaa24
Copy link

maenpaa24 commented Apr 16, 2019

Hi!

The package m4 needs a patch to meet the new glibc requirements. It has not been done officially so one has to do it manually. How should one modify the source code so that the patch is applied automatically?

The patch can me summarize to execute this inside the m4 folder:

sed -i 's/IO_ftrylockfile/IO_EOF_SEEN/' lib/*.c
echo "#define _IO_IN_BACKUP 0x100" >> lib/stdio-impl.h

Info gathered from http://www.linuxfromscratch.org/lfs/view/development/chapter06/m4.html

@maenpaa24 maenpaa24 reopened this Apr 16, 2019
@maenpaa24 maenpaa24 changed the title m4 requires a patch to update it to the newest glibc This issue can be deleted Apr 16, 2019
@maenpaa24 maenpaa24 reopened this Apr 16, 2019
@maenpaa24 maenpaa24 changed the title This issue can be deleted m4 requires a patch to update it to the newest glibc Apr 16, 2019
@oom-is
Copy link

oom-is commented Oct 23, 2019

I think you've seen other relevant traffic, but just in case: The m4/glibc issue you've noted is due to an outdated Buildroot target from 2017.

Please take a look at my "integ" branch (latest binary releases) or in @ChubbyAnt's fork (latest binary releases), both of which use an updated Buildroot target (2019.02.6 LTS) and an updated Linux kernel (4.14.146 in the 4.14 LTS series).

ChubbyAnt's releases/tree are only tested on NVME+Windows, while mine are tested on Windows&Linux but primarily SATA. If these don't fix your issues then please follow up.

NOTE that both of these forks also use SHA512 for password hashing, which means they're not backward compatible with 1.15.1 "vanilla". You'll need to uninstall (actually revert, preferably --revertnoerase then --revertTPer) the DTA 1.15.1 SEDutil before attempting to install the updated SEDutil PBA.

@r0m30 r0m30 closed this as completed Aug 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants