From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: pmacct marked as SKIP during IPFire build Date: Thu, 15 Jul 2021 17:40:17 +0100 Message-ID: <05DFA074-F1F8-4603-865B-FA76CEA596C3@ipfire.org> In-Reply-To: <897ed39a-1fcd-816a-a02c-e42052511659@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3677350293754022092==" List-Id: --===============3677350293754022092== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, This is just a warning that is being treated as an error. GCC seems to get the size calculation wrong, but it generally doesn=E2=80=99t= look like good coding style. Could you try this patch? https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/libcdada/files/libcda= da-0.3.4-Werror.patch -Michael > On 15 Jul 2021, at 17:10, Adolf Belka wrote: >=20 > Hi Michael, All, >=20 > On 15/07/2021 14:53, Adolf Belka wrote: >> Hi Michael, >>=20 >> On 15/07/2021 13:55, Michael Tremer wrote: >>> Hey, >>>=20 >>> I am not the export here, but I believe this was disabled because libcdad= a does not build with GCC 11. >>>=20 >>> Is there an update maybe? >> I have had a look and there is an update for libcdada. Doesn't mention any= thing about problems with gcc in its changelog. >> Will give a go to testing with existing and also with the new libcdada ver= sion and see how it goes. >>>=20 > So I took out the SUP_ARCH lines and did a build with both libcdada-0.3.4 a= nd libcdada-0.3.5 and got the same error with both. >>> You can just enable it again (remove the SUP_ARCHES line) and see what ha= ppens. Feel free to post the log here. >=20 > The log for the 0.3.4 version is at the end of this email. >=20 > There is a line about all warnings being treated as errors and searching on= that it seems that might be a consequence of GCC 11. My internet search seem= ed to indicate that will happen with GCC 11 if you have Werror in the flags a= nd that is present in both CFLAGS and CXXFLAGS. The suggestion in those posts= I read was to remove the Werror entry from the two sets of flags but as I am= not experienced with those types of things I thought I would ask here. >=20 > The actual error or warning appears to be related to a variable that is bei= ng flagged that it might exceed the maximum object size. You can find the err= or message near the end of the log below. >=20 > There were also a lot of warnings in the autogen.sh part of the build with = obsolete macros being flagged up and suggestion to run autoupdate. I tried pu= tting that after the autogen.sh line but it made no difference to the error t= hat stopped the build, although it might be good to also have in place. >=20 > Any suggestions for things to try out will be gladly welcomed. >=20 > Regards, >=20 > Adolf. >=20 >> Will do so if I have any problems. >>=20 >> Thanks for the info. >>=20 >> Regards, >> Adolf. >>>=20 >>> Best, >>> -Michael >>>=20 >>>> On 15 Jul 2021, at 11:58, Adolf Belka wrote: >>>>=20 >>>> Hi All, >>>>=20 >>>> I have been doing some update builds and while doing that with "next" I = noticed that pmacct and its dependency libcdada were both marked as SKIP and = so didn't get built. >>>>=20 >>>> What is the reason for this? Has there been some problem that needs to b= e fixed? >>>>=20 >>>>=20 >>>> Regards, >>>>=20 >>>> Adolf. >>>>=20 >>>=20 > --===============3677350293754022092==--