[llvm-dev] is it possible to disable build builtins-i386 when gnu/stubs-32.h is not ready?
Schrodinger ZHU Yifan via llvm-dev
llvm-dev at lists.llvm.org
Fri Dec 10 06:48:45 PST 2021
It works. But I encountered some other errors. I will report them back in a separate thread.
Schrodinger ZHU Yifan
School of Data Science, CUHK(SZ)
Website: https://zhuyi.fan
Github: SchrodingerZhu
Twitter: ZhuSchrodinger
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, December 10th, 2021 at 5:10 PM, David Spickett <david.spickett at linaro.org> wrote:
> Does the cmake option suggested here help?
>
> https://lists.llvm.org/pipermail/llvm-dev/2021-December/154077.html
>
> On Fri, 10 Dec 2021 at 01:02, Schrodinger ZHU Yifan via llvm-dev
>
> llvm-dev at lists.llvm.org wrote:
>
> > Hi,
> >
> > I do not know why CentOS is doing this, but on particular OS, <gnu/stubs-32.h> is provided in glibc-devel.i686, which includes all crt objects in the same time. Hence, installing that single lib for that particular header will actually pollute the system-wise CRT. In my situation, it seems that i386 related compiler-rt libs are not really concerned. So do we have options to disable i386 targets?
> >
> > Schrodinger ZHU Yifan
> >
> > School of Data Science, CUHK(SZ)
> >
> > Website: https://github.com/schrodingerzhu
> >
> > Github: SchrodingerZhu
> >
> > Twitter: ZhuSchrodinger
> >
> > Sent with ProtonMail Secure Email.
> >
> > LLVM Developers mailing list
> >
> > llvm-dev at lists.llvm.org
> >
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: publickey - i at zhuyi.fan - 0xE405E45C.asc
Type: application/pgp-keys
Size: 3237 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20211210/8a78cb0b/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 855 bytes
Desc: OpenPGP digital signature
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20211210/8a78cb0b/attachment.sig>
More information about the llvm-dev
mailing list