From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: $(UPDATE_AUTOMAKE) Date: Mon, 08 Mar 2021 15:02:58 +0000 Message-ID: <2B98249F-0B56-46CA-9BC5-A725D1B72B38@ipfire.org> In-Reply-To: <48b7ec4f-35c7-d392-38cc-32d60f14f9b1@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0847932168357891482==" List-Id: --===============0847932168357891482== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hey Adolf, Great question, but the answer is no. This is something that was required for the RISC-V port that I did and since = the changes do not do anything on the other architectures, I merged the branc= h and was planning to write an announcement to the list. Since I am quite buried in work at the moment, I didn=E2=80=99t not find to w= rite the announcement, yet. The macro simply updates the bundled automake scripts that come with the sour= ce tarballs of all those packages that use automake. They simply check whethe= r the architecture the script is running on is supported and older versions r= eport that they do not recognise this architecture at all. Therefore I simply= replace them with a recent version from our version of automake and the buil= d runs through. Some more packages might need it, but we will see it when it happens. There p= robably won=E2=80=99t be too regular builds of RISC-V anyways, so there is no= thing to worry about. But good to ask this :) -Michael > On 8 Mar 2021, at 13:11, Adolf Belka (ipfire) wr= ote: >=20 > Hi all, >=20 >=20 > I saw a lot of lfs files having $(UPDATE_AUTOMAKE) added to them. This is p= resumably related to the recently upgraded automake package. Should I add $(U= PDATE_AUTOMAKE) to any package I am updating if it has not already been added= or is it only needed on the ones that have already been modified? >=20 >=20 > Regards, >=20 > Adolf. >=20 --===============0847932168357891482==--