From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: cairo causes next build crash
Date: Sun, 08 Mar 2020 11:36:12 +0000 [thread overview]
Message-ID: <AD5A92B8-F3AE-4C50-9756-CCBA70258916@ipfire.org> (raw)
In-Reply-To: <5dcab8e3-20a0-b085-bc14-de84a9f83bb6@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2701 bytes --]
Hi,
The last nightly build was successful. Is this the branch with an updated binutils?
https://nightly.ipfire.org/next/2020-03-05%2005:54:09%20+0000-b3bc092d/
-Michael
> On 7 Mar 2020, at 13:24, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello development list,
>
> for your information:
>
>> cairo (1.14.8) [ 29 ][ FAIL ]
>>
>> | ^~~~~~~~~~~~~~~~~~~
>> | bfd_set_section_vma
>> lookup-symbol.c:155:36: warning: passing argument 1 of 'bfd_section_size' from incompatible pointer type [-Wincompatible-pointer-types]
>> 155 | size = bfd_section_size (symtab->bfd, section);
>> | ~~~~~~^~~~~
>> | |
>> | bfd * {aka struct bfd *}
>> In file included from lookup-symbol.c:67:
>> /usr/include/bfd.h:1205:35: note: expected 'const asection *' {aka 'const struct bfd_section *'} but argument is of type 'bfd *' {aka 'struct bfd *'}
>> 1205 | bfd_section_size (const asection *sec)
>> | ~~~~~~~~~~~~~~~~^~~
>> lookup-symbol.c:155:12: error: too many arguments to function 'bfd_section_size'
>> 155 | size = bfd_section_size (symtab->bfd, section);
>> | ^~~~~~~~~~~~~~~~
>> In file included from lookup-symbol.c:67:
>> /usr/include/bfd.h:1205:1: note: declared here
>> 1205 | bfd_section_size (const asection *sec)
>> | ^~~~~~~~~~~~~~~~
>> cc1: some warnings being treated as errors
>> make[5]: *** [Makefile:613: libcairo_trace_la-lookup-symbol.lo] Error 1
>> make[5]: Leaving directory '/usr/src/cairo-1.14.8/util/cairo-trace'
>> make[4]: *** [Makefile:975: all-recursive] Error 1
>> make[4]: Leaving directory '/usr/src/cairo-1.14.8/util'
>> make[3]: *** [Makefile:757: all] Error 2
>> make[3]: Leaving directory '/usr/src/cairo-1.14.8/util'
>> make[2]: *** [Makefile:897: all-recursive] Error 1
>> make[2]: Leaving directory '/usr/src/cairo-1.14.8'
>> make[1]: *** [Makefile:747: all] Error 2
>> make[1]: Leaving directory '/usr/src/cairo-1.14.8'
>> make: *** [cairo:74: /usr/src/log/cairo-1.14.8] Error 2
>>
>> ERROR: Building cairo [ FAIL ]
>> Check /home/pmu/devel/ipfire-2.x/log/_build.ipfire.log for errors if applicable [ FAIL ]
>
> Thanks, and best regards,
> Peter Müller
prev parent reply other threads:[~2020-03-08 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 13:24 Peter Müller
2020-03-08 11:36 ` Michael Tremer [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=AD5A92B8-F3AE-4C50-9756-CCBA70258916@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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