Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 3 Mar 2024 13:53:31 +0100
From:      Oliver Epper <oliver.epper@gmail.com>
To:        FreeBSD Ports <freebsd-ports@freebsd.org>
Subject:   compiling for other architecture
Message-ID:  <CAP8tsuQ=j4CSMno75nbh32-FEcvAtrrEDxup5d1u5n_3fibuuA@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
--00000000000042993a0612c119a1
Content-Type: text/plain; charset="UTF-8"

Hi all,

I am currently working on an updated port of net/pjsip. I have a personal
use case building for the raspberry-pi, too. All the information that I
found so far seemed outdated. Many are talking about building a
cross-compiler. With clang that should not be necessary, right?

Can anyone point me to more recent information on how I can build for armv6
on a x86_64 machine?

greetings
Oliver

P.S.: I know how to build for different architectures. My questions are all
about the "dos and don'ts" and best practices when it comes to the FreeBSDs
ports system.

--00000000000042993a0612c119a1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>I am currently working on an up=
dated port of net/pjsip. I have a personal use case building for the raspbe=
rry-pi, too. All the information that I found so far seemed outdated. Many =
are talking about building a cross-compiler. With clang that should not be =
necessary, right?</div><div><br></div><div>Can anyone point me to more rece=
nt information on how I can build for armv6 on a x86_64 machine?</div><div>=
<br></div><div>greetings</div><div>Oliver</div><div><br></div><div>P.S.: I =
know how to build for different architectures. My questions are all about t=
he &quot;dos and don&#39;ts&quot; and best practices when it comes to the F=
reeBSDs ports system.</div></div>

--00000000000042993a0612c119a1--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP8tsuQ=j4CSMno75nbh32-FEcvAtrrEDxup5d1u5n_3fibuuA>