From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Question regarding rootfile warning "Error! '/aarch64' in
 rootfiles files found!"
Date: Thu, 09 Dec 2021 20:39:57 +0100
Message-ID: <98b261ef-86dc-f60c-0dfc-8350749d563a@ipfire.org>
In-Reply-To: <93492c97-c04a-215a-c26e-908eaede6aa9@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3811439297482127847=="
List-Id: <development.lists.ipfire.org>

--===============3811439297482127847==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

P.S.: Bug #12743 (https://bugzilla.ipfire.org/show_bug.cgi?id=3D12743) has be=
en raised for this.

Should anybody have spare time to work on it, please feel free to do so. :-)

> Hello Adolf,
>=20
> thanks for your reply.
>=20
>> How should we deal with the situation where a source file filename happens=
 to use an architecture name the same as an IPFire name.
>=20
> I also think this is a false positive, though it surprises me we never came=
 across this
> scenario all the years before. Either way, make.sh (or whatever's doing thi=
s check) needs
> to be updated to ignore such cases.
>=20
> I'll file a bug for this later...
>=20
> Thanks, and best regards,
> Peter M=C3=BCller
>=20

--===============3811439297482127847==--