summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/pseudo/files/glibc238.patch
Commit message (Collapse)AuthorAgeFilesLines
* pseudo: Fix to work with glibc 2.40Richard Purdie2024-07-241-2/+8
| | | | | | | | | | glibc 2.40 renames some internal header variables. Update our hack to work with the new version. These kinds of problems illustrate we need to address the issue properly. (From OE-Core rev: 35021d650de3eecc3f42000181b39a5db5a8eaa0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Update to pull in gcc14 fix and missing statvfs64 interceptRichard Purdie2024-02-031-13/+0
| | | | | | | | | | | | | | | rpm 4.19 now builds with LFS64 support enabled by default, so it calls statvfs64() to get the space available on the filesystem it is installing packages into. This is not getting caught by pseudo, so rpm is checking the host's root filesystem, rather than the filesystem where the build is happening. Merge in that fix and a gcc14 fix. (From OE-Core rev: f6d021c860b2b99f46c604149317b326f493022d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Fix to work with glibc 2.38Richard Purdie2023-08-171-0/+72
This adds a horrible hack to get pseudo working with glibc 2.38. We can't drop _GNU_SOURCE to something like _DEFAULT_SOURCE since we need the defines the gnu options bring in. That leaves using internal glibc defines to disable the c23 versions of strtol/fscanf and friends. Which would break pseudo build with 2.38 from running on hosts with older glibc. We'll probably need to come up with something better but this gets glibc 2.38 and working and avoids autobuilder failures. (From OE-Core rev: 596fb699d470d7779bfa694e04908929ffeabcf7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>