Hi Michael,

On 19/04/2021 11:55, Michael Tremer wrote:

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=32a72d4ca8...

I used the patch from the above commit and it solved the hyperscan problem but then I next hit qemu failing to build. It seems to be doing things around meson even though the lfs is defined with autotools and both can be used. Attached is the log file for the qemu build. I can see the error in the logfile but I can't figure out what is causing the error to occur and therefore can't figure out how to stop it.

Any suggestions gladly welcomed.

Regards,

Adolf.

-Michael

...

On 17 Apr 2021, at 21:53, Adolf Belka adolf.belka@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.