Re: Trick: How to get i386-only software via dports

[Gavin Reade <greadey@xxxxxxxxx>]

--047d7b10cc593d9f0804de7bd0f5
Content-Type: text/plain; charset=ISO-8859-1

Well here is a tricky one - i'm running i386 DFly 3.4 on a P4 (i586) - as
reported by dmesg.  Sysinfo reports an i386 proceesor, but I am using
dports right from the beginning of the install. I've had no trouble
installing dports on this machine  (not that i've gone mad but - in terms
of a desktop which is what I'm trying to achieve - everything seems Ok so
far).  All I've ever done is pkg install [whatever] and it has worked.
 Funnily enough when I first installed the OS I could not install anything
with pkgsrc since it kept complaining that the software was built for 3.3
not 3.4 (I didn't check the repository date mind you!).
Anyway as far as dports is concerned I've had no problems.


On Mon, Jun 3, 2013 at 10:19 AM, John Marino <dragonflybsd@marino.st> wrote:

> As I have previously mentioned, only ports that can be built on x86_64 are
> eligible for dports.  This eliminates i386-only ports in the FreeBSD ports
> collection.
>
> So there won't be any pre-built binaries, but if one is desperate for some
> of these i386-only ports, there may be a way.  I have ported "portsnap"
> which can be used to quickly install FreeBSD ports at /usr/ports.  These
> FreeBSD ports use /usr/dports/Mk so it's possible to build FreeBSD ports
> straight on DragonFly.  Here's any example of how to build i386 software
> from /usr/ports from source:
>
> 1) cd /usr/dports/ports-mgmt/**portsnap
> 2) make install
> 3) rehash
> 4) portsnap fetch extract
> 5) cd /usr/ports/editors/e3
> 6) make install
> 7) rehash
> 8) e3
>
> Not every port is going to work.  Many ports that made it into dports
> needed additional flags and/or patches, and the same may be true for the
> i386 port you attempt.  However, there's a good chance some of these ports
> build without modifications.
>
> Also, those interested in helping to get some ports into dports can copy
> the directories from /usr/ports to /usr/dports in order to work on the
> necessary patches to pass back to us.
>
> John
>

--047d7b10cc593d9f0804de7bd0f5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Well here is a tricky one - i&#39;m running i386 DFly 3.4 =
on a P4 (i586) - as reported by dmesg. =A0Sysinfo reports an i386 proceesor=
, but I am using dports right from the beginning of the install. I&#39;ve h=
ad no trouble installing dports on this machine =A0(not that i&#39;ve gone =
mad but - in terms of a desktop which is what I&#39;m trying to achieve - e=
verything seems Ok so far). =A0All I&#39;ve ever done is pkg install [whate=
ver] and it has worked. =A0Funnily enough when I first installed the OS I c=
ould not install anything with pkgsrc since it kept complaining that the so=
ftware was built for 3.3 not 3.4 (I didn&#39;t check the repository date mi=
nd you!).<div style>
Anyway as far as dports is concerned I&#39;ve had no problems.</div></div><=
div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Jun 3,=
 2013 at 10:19 AM, John Marino <span dir=3D"ltr">&lt;<a href=3D"mailto:drag=
onflybsd@marino.st" target=3D"_blank">dragonflybsd@marino.st</a>&gt;</span>=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">As I have previously mentioned, only ports t=
hat can be built on x86_64 are eligible for dports. =A0This eliminates i386=
-only ports in the FreeBSD ports collection.<br>

<br>
So there won&#39;t be any pre-built binaries, but if one is desperate for s=
ome of these i386-only ports, there may be a way. =A0I have ported &quot;po=
rtsnap&quot; which can be used to quickly install FreeBSD ports at /usr/por=
ts. =A0These FreeBSD ports use /usr/dports/Mk so it&#39;s possible to build=
 FreeBSD ports straight on DragonFly. =A0Here&#39;s any example of how to b=
uild i386 software from /usr/ports from source:<br>

<br>
1) cd /usr/dports/ports-mgmt/<u></u>portsnap<br>
2) make install<br>
3) rehash<br>
4) portsnap fetch extract<br>
5) cd /usr/ports/editors/e3<br>
6) make install<br>
7) rehash<br>
8) e3<br>
<br>
Not every port is going to work. =A0Many ports that made it into dports nee=
ded additional flags and/or patches, and the same may be true for the i386 =
port you attempt. =A0However, there&#39;s a good chance some of these ports=
 build without modifications.<br>

<br>
Also, those interested in helping to get some ports into dports can copy th=
e directories from /usr/ports to /usr/dports in order to work on the necess=
ary patches to pass back to us.<span class=3D"HOEnZb"><font color=3D"#88888=
8"><br>

<br>
John<br>
</font></span></blockquote></div><br></div>

--047d7b10cc593d9f0804de7bd0f5--