From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problems with hyperscan when building binutils
Date: Mon, 19 Apr 2021 10:55:34 +0100 [thread overview]
Message-ID: <A53B5F8E-1163-4031-AB22-654D3B0EA8FD@ipfire.org> (raw)
In-Reply-To: <1af51d7a-904b-737c-e005-f645b2151b8b@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
Hello,
Yes it is.
I ran into this in my toolchain branch where I am collecting updates for all sorts of tools related to this.
You can cherry-pick the following commit and hyperscan builds again:
https://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=commitdiff;h=32a72d4ca8a9d1387ebf3b3cca5b3c54b3b83324
-Michael
> On 17 Apr 2021, at 21:53, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi All,
>
> It definitely is related to the new binutils in some way. Doing a git restore to the current binutils and redoing the clean and make results in hyperscan building without any problems.
>
> Regards,
>
> Adolf
>
> On 17/04/2021 16:11, Adolf Belka wrote:
>> Hi All,
>>
>> I was building an update of binutils. That built successfully but then hyperscan had a lot of failures. I am not able to understand what the problem is from the error messages.
>>
>> Could this be related to my update of binutils?
>>
>> If yes then what do I need to change?
>>
>> If no then what is causing the problem?
>>
>> I did a git pull origin next before I did my build of binutils.
>>
>> Error log attached.
>>
>>
>> Regards,
>>
>> Adolf.
>>
next prev parent reply other threads:[~2021-04-19 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 14:11 Adolf Belka
2021-04-17 20:53 ` Adolf Belka
2021-04-19 9:55 ` Michael Tremer [this message]
2021-04-20 17:30 ` Adolf Belka
[not found] <9e299f6ca9e27efdde6ef0ae532cba63@web.de>
2021-04-21 13:42 ` Adolf Belka
2021-04-21 13:57 ` Adolf Belka
2021-04-21 14:23 ` Michael Tremer
2021-04-21 15:50 ` Adolf Belka
2021-04-21 15:52 ` Michael Tremer
2021-04-21 21:14 ` Adolf Belka
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=A53B5F8E-1163-4031-AB22-654D3B0EA8FD@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