This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Buildbot Update
- From: Christophe Lyon <christophe dot lyon at linaro dot org>
- To: Paulo Matos <pmatos@linki.tools>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 20 Dec 2017 11:09:31 +0100
- Subject: Re: GCC Buildbot Update
- Authentication-results: sourceware.org; auth=none
- References: <f664b74e-8751-24ed-139f-443ce3f1cdef@linki.tools> <CAKdteObvKKTJrpq2Mod-9H37QpiT2gPshgfeztWJvi-XLQE-sw@mail.gmail.com> <61dee997-5760-63ac-8a7d-d901e60fa771@linki.tools> <CAKdteObuo4w9NmNE7B7m5ACNBmTF+khNscGtGZ7sG7msVL3q-g@mail.gmail.com> <be5b763f-649f-c27a-c73b-6cc2affc6161@linki.tools> <CAKdteOZnoDdFZP86xnQLq+kgbi3xp=SuifswW1PmAdvgKVr7Ug@mail.gmail.com> <2b92a1ae-0f24-7c70-67e8-64d9105c8123@linki.tools>
On 20 December 2017 at 11:02, Paulo Matos <pmatos@linki.tools> wrote:
>
>
> On 20/12/17 10:51, Christophe Lyon wrote:
>>
>> The recent fix changed the Makefile and configure script in libatomic.
>> I guess that if your incremental builds does not run configure, it's
>> still using old Makefiles, and old options.
>>
>>
> You're right. I guess incremental builds should always call configure,
> just in case.
>
Maybe, but this does not always work. Sometimes, I have to rm -rf $builddir
> Thanks,
> --
> Paulo Matos