From: "Martin Liška" <mliska@suse.cz>
To: Ulf Samuelsson <binutils@emagii.com>,
Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org
Subject: Re: [PATCH v12 0/11 Add support for CRC64 generation in linker
Date: Wed, 8 Mar 2023 10:31:28 +0100 [thread overview]
Message-ID: <9e098af0-2aec-8570-ee5c-439c39738284@suse.cz> (raw)
In-Reply-To: <22f15ceb-e5db-8fd8-94a2-57e87cea6574@emagii.com>
On 3/7/23 19:08, Ulf Samuelsson via Binutils wrote:
>
> On 2023-03-07 14:59, Nick Clifton wrote:
>> Hi Ulf,
>>
>>> Patchset XII
>>> testsuite fixed to skip some tests.
>>
>> Thanks. I have now applied your patch set.
>>
>> I made some small changes, mostly code formatting and correcting
>> some of the error messages.
>>
>> Thank you very much for persisting with this patch contribution.
>>
> The Buildbot reports errors though!
>
> Best Regards
>
> Ulf Samuelsson
>
>
>> Cheers
>> Nick
>>
>>
Hi.
I think this patch set caused the following build failure:
[ 173s] gcc -DHAVE_CONFIG_H -I. -I../../ld -I. -I../../ld -I../bfd -I../../ld/../bfd -I../../ld/../include -fomit-frame-pointer -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -Wno-error -DLOCALEDIR="\"/usr/share/locale\"" -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Werror -DELF_LIST_OPTIONS=true -DELF_SHLIB_LIST_OPTIONS=false -DELF_PLT_UNWIND_LIST_OPTIONS=false -fomit-frame-pointer -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -Wno-error -MT ldcrc64.o -MD -MP -MF .deps/ldcrc64.Tpo -c -o ldcrc64.o ../../ld/ldcrc64.c
[ 173s] ../../ld/ldcrc64.c:109:1: error: conflicting types for 'init_crc64_tab'; have 'uint64_t *(algorithm_desc_t *)' {aka 'long long unsigned int *(algorithm_desc_t *)'}
[ 173s] 109 | init_crc64_tab (algorithm_desc_t * dsc)
[ 173s] | ^~~~~~~~~~~~~~
[ 173s] In file included from ../../ld/ldcrc64.c:33:
[ 173s] ../../ld/lddigest.h:166:17: note: previous declaration of 'init_crc64_tab' with type 'bfd_vma *(algorithm_desc_t *)' {aka 'long unsigned int *(algorithm_desc_t *)'}
[ 173s] 166 | extern bfd_vma *init_crc64_tab (algorithm_desc_t * dsc);
[ 173s] | ^~~~~~~~~~~~~~
[ 173s] ../../ld/ldcrc64.c:140:10: error: conflicting types for 'calc_crc64'; have 'uint64_t(algorithm_desc_t *, const unsigned char *, size_t)' {aka 'long long unsigned int(algorithm_desc_t *, const unsigned char *, unsigned int)'}
[ 173s] 140 | uint64_t calc_crc64
[ 173s] | ^~~~~~~~~~
[ 173s] ../../ld/lddigest.h:167:16: note: previous declaration of 'calc_crc64' with type 'bfd_vma(algorithm_desc_t *, const unsigned char *, size_t)' {aka 'long unsigned int(algorithm_desc_t *, const unsigned char *, unsigned int)'}
[ 173s] 167 | extern bfd_vma calc_crc64
[ 173s] | ^~~~~~~~~~
[ 173s] make[4]: *** [Makefile:1604: ldcrc64.o] Error 1
[ 173s] make[4]: Leaving directory '/home/abuild/rpmbuild/BUILD/binutils-2.40.50/build-dir/ld'
that happens on i586-linux-gnu host if I configure with --target=avr
Can you please take a look?
Thanks,
Martin
next prev parent reply other threads:[~2023-03-08 9:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 13:31 binutils
2023-03-06 13:31 ` [PATCH v12 01/11] DIGEST: LICENSING binutils
2023-03-06 13:31 ` [PATCH v12 02/11] DIGEST: NEWS binutils
2023-03-06 13:31 ` [PATCH v12 03/11] DIGEST: Documentation binutils
2023-03-06 13:31 ` [PATCH v12 04/11] DIGEST: testsuite binutils
2023-03-06 13:31 ` [PATCH v12 05/11] DIGEST: ldlex.l binutils
2023-03-06 13:31 ` [PATCH v12 06/11] DIGEST: ldgram.y binutils
2023-03-06 13:31 ` [PATCH v12 07/11] DIGEST: ldmain.c binutils
2023-03-06 13:31 ` [PATCH v12 08/11] DIGEST: ldlang.*: add timestamp binutils
2023-03-06 13:31 ` [PATCH v12 09/11] DIGEST: calculation binutils
2023-03-06 13:31 ` [PATCH v12 10/11] DIGEST: Makefile.* binutils
2023-03-06 13:31 ` [PATCH v12 11/11] Build ldint binutils
2023-03-07 13:59 ` [PATCH v12 0/11 Add support for CRC64 generation in linker Nick Clifton
2023-03-07 18:03 ` Ulf Samuelsson
2023-03-07 18:08 ` Ulf Samuelsson
2023-03-08 9:31 ` Martin Liška [this message]
2023-03-08 11:48 ` Ulf Samuelsson
2023-03-08 12:52 ` Nick Clifton
2023-03-08 13:23 ` Ulf Samuelsson
2023-03-08 12:57 ` Alan Modra
2023-03-08 13:39 ` Ulf Samuelsson
2023-03-09 8:48 ` Ulf Samuelsson
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=9e098af0-2aec-8570-ee5c-439c39738284@suse.cz \
--to=mliska@suse.cz \
--cc=binutils@emagii.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/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).