This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> Turns out Arch Linux uses the build-programs variable to build > different parts of glibc with different flags; but setting > build-programs to "no" also disables the default rules for programs, > leading to makefile-related errors elsewhere. Thanks for figuring out my issue, this patch works for me. :) In case anyone's interested, this is how we do the build: https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/glibc&id=45447dc6eaa2d53b452df96ec041c5b5f4977b6c#n84 Given that it's an officially supported build option permutation, it might be worth adding some variations like this (especially for something that changes how the makefiles operate in general) to e.g. build-many-glibcs.py, and having this automatically get tested by some continuous integration buildbot. (I have no idea how glibc organizes this stuff in general, whether developers run smoketests on their own computer or if there's some resource to do it without babysitting.) ... Also repeating for permanent record what was said on IRC, given the use case of disabling fortify for the libraries, maybe someone with more knowledge of glibc than me, could write a patch for something like --with-nonshared-cflags=CFLAGS except for non-libraries. -- Eli Schwartz Bug Wrangler and Trusted User
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |