Trick: How to get i386-only software via dports

[Gavin Reade]

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 at 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20130607/32d3e109/attachment-0002.html>