<div dir="ltr">Thanks for that John,<div><br></div><div style>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;</div>
<div style><br></div><div style><div>vlad# make</div><div>===> ghc-7.6.3 depends on file: /usr/local/share/xsl/docbook/html - found</div><div>===> ghc-7.6.3 depends on file: /usr/local/bin/xsltproc - found</div>
<div>===> ghc-7.6.3 depends on executable: gmake - found</div><div>===> ghc-7.6.3 depends on file: /usr/local/bin/as - found</div><div>===> ghc-7.6.3 depends on file: /usr/local/bin/perl5.14.2 - found</div>
<div>===> ghc-7.6.3 depends on file: /usr/local/bin/autoconf-2.69 - found</div><div>===> ghc-7.6.3 depends on file: /usr/local/bin/autoconf - found</div><div>===> ghc-7.6.3 depends on executable: gm4 - found</div>
<div>===> ghc-7.6.3 depends on shared library: gmp.10 - found</div><div>===> ghc-7.6.3 depends on shared library: ffi.6 - found</div><div>===> ghc-7.6.3 depends on shared library: iconv.3 - found</div><div>
===> Configuring for ghc-7.6.3</div><div>configure: loading site script /usr/dports/Templates/config.site</div><div>checking for path to top of build tree... ELF interpreter /libexec/ld-elf.so.1 not found</div><div>Abort trap: 6</div>
<div>configure: error: cannot determine current directory</div><div>*** Error code 1</div><div><br></div><div>Stop.</div><div>make: stopped in /usr/ports/lang/ghc</div><div><br></div><div><div>vlad# find / -name "ld-elf.so*"</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, but the FreeBSD make can't find it. </div><div style><br></div><div style>
<br></div><div style>thanks,</div><div style><br></div><div style>gavin</div><div style><br></div><div style> </div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 6, 2013 at 11:10 PM, John Marino <span dir="ltr"><<a href="mailto:dragonflybsd@marino.st" target="_blank">dragonflybsd@marino.st</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 6/6/2013 14:54, Gavin Reade wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Well here is a tricky one - i'm running i386 DFly 3.4 on a P4 (i586) -<br>
as reported by dmesg. Sysinfo reports an i386 proceesor, but I am using<br>
dports right from the beginning of the install. I've had no trouble<br>
installing dports on this machine (not that i've gone mad but - in<br>
terms of a desktop which is what I'm trying to achieve - everything<br>
seems Ok so far). All I've ever done is pkg install [whatever] and it<br>
has worked. Funnily 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't check the repository date mind you!).<br>
Anyway as far as dports is concerned I've had no problems.<br>
</blockquote>
<br></div>
Great, I'm glad to hear it!<br>
You may have misunderstood the previous post though. i386 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. 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.<br>
<br>
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.<br>
<br>
Regards,<br>
John<br>
</blockquote></div><br></div>