From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer <michael.tremer@ipfire.org> To: development@lists.ipfire.org Subject: Re: Problems with hyperscan when building binutils Date: Wed, 21 Apr 2021 16:52:43 +0100 Message-ID: <CB46F198-B0BB-4050-98E3-9109A6405F00@ipfire.org> In-Reply-To: <2c7e10d5-83e5-2587-6227-a8e9e67fc328@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6493540143845418489==" List-Id: <development.lists.ipfire.org> --===============6493540143845418489== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, This is what I went with: https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dcommitdiff;h=3Dd578a= 55d345d9b9744592c87be4dc593ca05084f -Michael > On 21 Apr 2021, at 16:50, Adolf Belka <adolf.belka(a)ipfire.org> wrote: >=20 > Hi Michael, >=20 > On 21/04/2021 16:23, Michael Tremer wrote: >> Hello, >> I have a (similar?) patch here: >> https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dcommitdiff;h=3D48= dfb9059e493b6ee5d16515d4b485448cd7a38f >> You can just cherry-pick that one, too. > Yes it looks like the one I got from the qemu github. That patch worked and= qemu built. >=20 > Now it has stopped at strace. > It looks like it is not possible to now enable m32 personality support. >=20 > checking for m32 personality compile support (using gcc -I./bundled/linux/= arch/x86/include/uapi -I./bundled/linux/include/uapi -Isrc -m32)... yes > checking for m32 personality runtime support... no > checking whether mpers.sh m32 -m32 works... mpers-m32/sample_struct.d2: ind= ex [ ] without special > no > checking whether to enable m32 personality support... no > configure: error: Cannot enable m32 personality support > make: *** [strace:81: /usr/src/log/strace-5.11] Error 1 >=20 > The default configure for strace is yes for m32 support and for several yea= rs strace enforces mpers support by default. >=20 > It looks like I can use --disable-mpers or --enable-mpers=3Dcheck to overco= me that. > Before I do that I would just like confirmation that this is okay to do or = if there is a way to get m32 runtime support on IPFire if it is needed. > As it is related to 32 bit I could imagine that it will not be needed after= the end of this year anyway >=20 > Regards, > Adolf >> -Michael >>> On 21 Apr 2021, at 14:57, Adolf Belka <adolf.belka(a)ipfire.org> wrote: >>>=20 >>> Hi All, >>>=20 >>> I have found a patch in the qemu github which is named >>>=20 >>> 0004-build-no-pie-is-no-functional-linker-flag.patch >>>=20 >>> and the description seems very similar if not exact to what I am getting.= It mentions an update of binutils triggering the problem. This is from back = in Dec 2020. >>>=20 >>> I will try this patch out in my build and let you know how things go. >>>=20 >>> Regards, >>>=20 >>> Adolf. >>>=20 >>> On 21/04/2021 15:42, Adolf Belka wrote: >>>> Hi Marcel, >>>>=20 >>>> On 21/04/2021 07:43, Marcel Lorenz wrote: >>>>> Hi Addolf, >>>>>=20 >>>>> look here: >>>>> https://git.ipfire.org/?p=3Dpeople/mlorenz/ipfire-2.x.git;a=3Dcommitdif= f;h=3Da537670fd2a709b4e4adc188b09165319a67bb49 >>>> Thanks for the patch information. One of those patches was the one I had= already got from Michael. I added the other patch into my build but got the = same result. Hyperscan builds fine but qemu fails. The same errors have occur= red, the first one being >>>>=20 >>>> BUILD multiboot.img >>>> ld: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?) >>>> make[3]: *** [Makefile:57: multiboot.img] Error 1 >>>>=20 >>>> and the second >>>>=20 >>>> make[2]: *** [Makefile:206: pc-bios/optionrom/all] Error 2 >>>> make[2]: *** Waiting for unfinished jobs.... >>>>=20 >>>> Full log for qemu from this build attached. >>>>=20 >>>> Regards, >>>> Adolf. >>>>=20 >>>>>=20 >>>>> Regards, >>>>>=20 >>>>> Marcel >>>>>=20 >>>>> Am 20.4.2021 19:30, schrieb Adolf Belka: >>>>>=20 >>>>>> Hi Michael, >>>>>>=20 >>>>>> On 19/04/2021 11:55, Michael Tremer wrote: >>>>>>=20 >>>>>>> Hello, >>>>>>>=20 >>>>>>> Yes it is. >>>>>>>=20 >>>>>>> I ran into this in my toolchain branch where I am collecting updates >>>>>>> for all sorts of tools related to this. >>>>>>>=20 >>>>>>> You can cherry-pick the following commit and hyperscan builds again: >>>>>>>=20 >>>>>>> https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dcommitdiff;h= =3D32a72d4ca8a9d1387ebf3b3cca5b3c54b3b83324 >>>>>> 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. >>>>>>=20 >>>>>> Any suggestions gladly welcomed. >>>>>>=20 >>>>>> Regards, >>>>>>=20 >>>>>> Adolf. >>>>>> -Michael >>>>>>=20 >>>>>> On 17 Apr 2021, at 21:53, Adolf Belka <adolf.belka(a)ipfire.org> wrote: >>>>>>=20 >>>>>> Hi All, >>>>>>=20 >>>>>> 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. >>>>>>=20 >>>>>> Regards, >>>>>>=20 >>>>>> Adolf >>>>>>=20 >>>>>> On 17/04/2021 16:11, Adolf Belka wrote: Hi All, >>>>>>=20 >>>>>> 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. >>>>>>=20 >>>>>> Could this be related to my update of binutils? >>>>>>=20 >>>>>> If yes then what do I need to change? >>>>>>=20 >>>>>> If no then what is causing the problem? >>>>>>=20 >>>>>> I did a git pull origin next before I did my build of binutils. >>>>>>=20 >>>>>> Error log attached. >>>>>>=20 >>>>>> Regards, >>>>>>=20 >>>>>> Adolf. --===============6493540143845418489==--