i checked with the original author of those tests, and basically: 1. he compiled an empty .c file into a .so, and checked that in as libtest_empty.so
2. then for each of the invalid files, he used a hex editor to corrupt a copy of the original libtest_empty.so file for obvious reasons, AOSP never accepts prebuilt blobs from contributors, so that's not a particularly useful path for you to spend any time on :-) a patch i could accept would be a patch that did the ELF file modification when the test runs instead --- we could check in the trivial .c file, add genrules to build the libtest_empty.so files, and genrules to corrupt them [probably just with hard-coded offsets and data in the build files]. ugly, and a fair amount of work, but better than what we have today, and something we should do at some point anyway! tbh though, i'd just ignore these files for now --- they're not needed to boot, only to pass CTS. if you're having trouble building because the build system's dependency analysis wants files to be present, just use empty files :-) On Monday, November 29, 2021 at 7:48:26 PM UTC-8 [email protected] wrote: > hello, > I wonder how to build the binaries under bionic/tests/prebuilt-elf-files? > I am working on aosp 12 and can not find the script and source code to > build these prebuilt binaries? > > Thanks in adv. > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/dba9b929-36b7-4f61-ba9c-7a78e7e03049n%40googlegroups.com.
