From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>, libc-alpha@sourceware.org
Subject: Re: [PING^2] [PATCH] build-many-glibcs.py: --disable-gcov for gcc-first
Date: Wed, 19 Apr 2023 09:06:04 -0300 [thread overview]
Message-ID: <1ca28aec-0829-5203-7f81-2aa381657b91@linaro.org> (raw)
In-Reply-To: <20230418185811.3w6yoj4cxa7cn6nq@lug-owl.de>
On 18/04/23 15:58, Jan-Benedict Glaw wrote:
> Hi!
>
> About another week, another ping.
>
> Thanks,
> Jan-Benedict
LGTM, thanks. I have installed it.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
>
> On Thu, 2023-04-13 17:46:40 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>> I want to ping this patch.
>> On Sat, 2023-04-01 21:09:19 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>>> I started using scripts/build-many-glibcs.py to do scheduled CI builds
>>> with --full-gcc and noticed that in my setup (fairly new host GCC
>>> version, and a small patch to use all-trunk versions for all relevant
>>> sources from a local GIT mirror), I run into an issue with gcc-first:
>>>
>>> /var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/bin/ar rc libgcc.a $objects
>>> /var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/bin/ranlib libgcc.a
>>> /var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/build/compilers/alpha-linux-gnu/gcc-first/./gcc/xgcc -B/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/build/compilers/alpha-linux-gnu/gcc-first/./gcc/ -B/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/bin/ -B/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/lib/ -isystem /var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/include -isystem /var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/install/compilers/alpha-linux-gnu/alpha-glibc-linux-gnu/sys-include -g -O2 -mieee -O2 -g -O2 -mieee -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -mieee -mfp-rounding-mode=d -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc -fPIC -mieee -mfp-rounding-mode=d -I. -I. -I../.././gcc -I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/src/gcc/libgcc -I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/src/gcc/libgcc/. -I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/src/gcc/libgcc/../gcc -I/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/src/gcc/libgcc/../include -DHAVE_CC_TLS -o _gcov_merge_add.o -MT _gcov_merge_add.o -MD -MP -MF _gcov_merge_add.dep -DL_gcov_merge_add -c /var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/src/gcc/libgcc/libgcov-merge.c
>>> In file included from /var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/src/gcc/libgcc/libgcov-merge.c:26:
>>> /var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/src/gcc/libgcc/libgcov.h:49:10: fatal error: sys/mman.h: No such file or directory
>>> 49 | #include <sys/mman.h>
>>> | ^~~~~~~~~~~~
>>> compilation terminated.
>>> make[3]: *** [Makefile:924: _gcov_merge_add.o] Error 1
>>> make[3]: Leaving directory '/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/build/compilers/alpha-linux-gnu/gcc-first/alpha-glibc-linux-gnu/libgcc'
>>> make[2]: *** [Makefile:13209: all-target-libgcc] Error 2
>>> make[2]: Leaving directory '/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/build/compilers/alpha-linux-gnu/gcc-first'
>>> make[1]: *** [Makefile:1023: all] Error 2
>>> make[1]: Leaving directory '/var/lib/laminar/run/glibcbot-alpha-linux-gnu/20/build/compilers/alpha-linux-gnu/gcc-first'
>>>
>>> FAIL: compilers-alpha-linux-gnu gcc-first build
>>>
>>>
>>> I found a long-standing PR for GCC:
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100289 . Maybe it would
>>> be okay to pass --disable-gcov to overcome this?
>>>
>>>
>>> diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
>>> index 29c10c2916..b29e32e7bd 100755
>>> --- a/scripts/build-many-glibcs.py
>>> +++ b/scripts/build-many-glibcs.py
>>> @@ -1483,6 +1483,7 @@ class Config(object):
>>> '--disable-threads',
>>> '--disable-libatomic',
>>> '--disable-decimal-float',
>>> + '--disable-gcov',
>>> '--disable-libffi',
>>> '--disable-libgomp',
>>> '--disable-libitm',
>>>
>>> This gets me past this build step.
>>>
>>> Thanks,
>>> Jan-Benedict
>>>
>>> --
>>
>>
>>
>> --
>
>
>
prev parent reply other threads:[~2023-04-19 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 19:09 Jan-Benedict Glaw
2023-04-04 12:48 ` Adhemerval Zanella Netto
2023-04-13 15:46 ` [PING] " Jan-Benedict Glaw
2023-04-18 18:58 ` [PING^2] " Jan-Benedict Glaw
2023-04-19 12:06 ` Adhemerval Zanella Netto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ca28aec-0829-5203-7f81-2aa381657b91@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=jbglaw@lug-owl.de \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).