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

[Gavin Reade <greadey@xxxxxxxxx>]

--485b395e7ea7835d7804de89e9d6
Content-Type: text/plain; charset=ISO-8859-1

Thanks for that John,

You're absolutely right, I competely missed your point!!!!!  Anyway I tried
building ghc form dports - it works after a fashion but there was no ghci
(took days and days as well :-)), so I tried your recipe.  I got the
following error after "portsnap fetch extract" and then cd in to ghc dir in
ports;

vlad# make
===>   ghc-7.6.3 depends on file: /usr/local/share/xsl/docbook/html - found
===>   ghc-7.6.3 depends on file: /usr/local/bin/xsltproc - found
===>   ghc-7.6.3 depends on executable: gmake - found
===>   ghc-7.6.3 depends on file: /usr/local/bin/as - found
===>   ghc-7.6.3 depends on file: /usr/local/bin/perl5.14.2 - found
===>   ghc-7.6.3 depends on file: /usr/local/bin/autoconf-2.69 - found
===>   ghc-7.6.3 depends on file: /usr/local/bin/autoconf - found
===>   ghc-7.6.3 depends on executable: gm4 - found
===>   ghc-7.6.3 depends on shared library: gmp.10 - found
===>   ghc-7.6.3 depends on shared library: ffi.6 - found
===>   ghc-7.6.3 depends on shared library: iconv.3 - found
===>  Configuring for ghc-7.6.3
configure: loading site script /usr/dports/Templates/config.site
checking for path to top of build tree... ELF interpreter
/libexec/ld-elf.so.1 not found
Abort trap: 6
configure: error: cannot determine current directory
*** Error code 1

Stop.
make: stopped in /usr/ports/lang/ghc

vlad# find / -name "ld-elf.so*"
/usr/libexec/ld-elf.so.1
/usr/libexec/ld-elf.so.2


so the library is on my system, but the FreeBSD make can't find it.


thanks,

gavin




On Thu, Jun 6, 2013 at 11:10 PM, John Marino <dragonflybsd@marino.st> wrote:

> On 6/6/2013 14:54, Gavin Reade wrote:
>
>> 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.
>>
>
> Great, I'm glad to hear it!
> You may have misunderstood the previous post though.  i386 is supported,
> it has a large package repository as you have discovered.
>
> What is missing from that repository are ports that are *only* for the
> i386.  We don't put them in dports.  Any port in dports should (in theory)
> build on both x86-64 and i386.  In practice, a few have errors building on
> i386 and we've got about 80 Haskell ports that don't build on i386 due to a
> known issue with GHC concerning TLS.
>
> What this trick does is enable a regular user such as yourself to try to
> build these i386-only ports on your via by source.  The example I used is
> e3 -- that's not in dports as it is marked i386-only.
>
> Regards,
> John
>

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

<div dir=3D"ltr">Thanks for that John,<div><br></div><div style>You&#39;re =
absolutely right, I competely missed your point!!!!! =A0Anyway I tried buil=
ding ghc form dports - it works after a fashion but there was no ghci (took=
 days and days as well :-)), so I tried your recipe. =A0I got the following=
 error after &quot;portsnap fetch extract&quot; and then cd in to ghc dir i=
n ports;</div>
<div style><br></div><div style><div>vlad# make</div><div>=3D=3D=3D&gt; =A0=
 ghc-7.6.3 depends on file: /usr/local/share/xsl/docbook/html - found</div>=
<div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on file: /usr/local/bin/xsltproc -=
 found</div>
<div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on executable: gmake - found</div>=
<div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on file: /usr/local/bin/as - found=
</div><div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on file: /usr/local/bin/perl=
5.14.2 - found</div>
<div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on file: /usr/local/bin/autoconf-2=
.69 - found</div><div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on file: /usr/loc=
al/bin/autoconf - found</div><div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on ex=
ecutable: gm4 - found</div>
<div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on shared library: gmp.10 - found<=
/div><div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on shared library: ffi.6 - fo=
und</div><div>=3D=3D=3D&gt; =A0 ghc-7.6.3 depends on shared library: iconv.=
3 - found</div><div>
=3D=3D=3D&gt; =A0Configuring for ghc-7.6.3</div><div>configure: loading sit=
e script /usr/dports/Templates/config.site</div><div>checking for path to t=
op of build tree... ELF interpreter /libexec/ld-elf.so.1 not found</div><di=
v>Abort trap: 6</div>
<div>configure: error: cannot determine current directory</div><div>*** Err=
or code 1</div><div><br></div><div>Stop.</div><div>make: stopped in /usr/po=
rts/lang/ghc</div><div><br></div><div><div>vlad# find / -name &quot;ld-elf.=
so*&quot;</div>
<div>/usr/libexec/ld-elf.so.1</div><div>/usr/libexec/ld-elf.so.2</div></div=
><div><br></div><div><br></div><div style>so the library is on my system, b=
ut the FreeBSD make can&#39;t find it.=A0</div><div style><br></div><div st=
yle>
<br></div><div style>thanks,</div><div style><br></div><div style>gavin</di=
v><div style><br></div><div style>=A0</div></div></div><div class=3D"gmail_=
extra"><br><br><div class=3D"gmail_quote">On Thu, Jun 6, 2013 at 11:10 PM, =
John Marino <span dir=3D"ltr">&lt;<a href=3D"mailto:dragonflybsd@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"><div class=3D"im">On 6/6/2013 14:54, Gavin R=
eade wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Well here is a tricky one - i&#39;m running i386 DFly 3.4 on a P4 (i586) -<=
br>
as reported by dmesg. =A0Sysinfo reports an i386 proceesor, but I am using<=
br>
dports right from the beginning of the install. I&#39;ve had no trouble<br>
installing dports on this machine =A0(not that i&#39;ve gone mad but - in<b=
r>
terms of a desktop which is what I&#39;m trying to achieve - everything<br>
seems Ok so far). =A0All I&#39;ve ever done is pkg install [whatever] and i=
t<br>
has worked. =A0Funnily enough when I first installed the OS I could not<br>
install anything with pkgsrc since it kept complaining that the software<br=
>
was built for 3.3 not 3.4 (I didn&#39;t check the repository date mind you!=
).<br>
Anyway as far as dports is concerned I&#39;ve had no problems.<br>
</blockquote>
<br></div>
Great, I&#39;m glad to hear it!<br>
You may have misunderstood the previous post though. =A0i386 is supported, =
it has a large package repository as you have discovered.<br>
<br>
What is missing from that repository are ports that are *only* for the i386=
. =A0We don&#39;t put them in dports. =A0Any port in dports should (in theo=
ry) build on both x86-64 and i386. =A0In practice, a few have errors buildi=
ng on i386 and we&#39;ve got about 80 Haskell ports that don&#39;t build on=
 i386 due to a known issue with GHC concerning TLS.<br>

<br>
What this trick does is enable a regular user such as yourself to try to bu=
ild these i386-only ports on your via by source. =A0The example I used is e=
3 -- that&#39;s not in dports as it is marked i386-only.<br>
<br>
Regards,<br>
John<br>
</blockquote></div><br></div>

--485b395e7ea7835d7804de89e9d6--