Timestamp:
08/25/2022 07:24:58 AM (2 years ago)
Author:
Pierre Labastie <pierre.labastie@…>
Branches:
11.2, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
d8c9a43f, e9d65f2f
Parents:
feed7fea
Message:

Don't use dummy.c for glibc sanity check in chap 5

It seems glibc creates dummy.c for its own use. This leaves some
dummy.xxx files in the directory, that may lead some users to think that
the directory is not properly cleaned up after the test (I did :)

So use a pipe so that only a.out is created

(No files)

Note: See TracChangeset for help on using the changeset viewer.