tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: compiler framework, fortran, libtool, and other headaches

Jon Buller <> writes:

> Dan McMahill wrote:
>> I recently added lang/gcc44 to pkgsrc with C, C++, OBJC, and
>> FORTRAN support.  Then I updated mk/compiler/
>> accordingly.  I used the entries for lang/gcc34 as an example
>> in for what to do about gcc44.
>> However, the more I have looked at this, the more problems I
>> see.  I'm wondering if I have just confused myself or if we
>> have a more fundamental problem we need to address.
>> [snip]
>> Comments?  Suggestions?
> I had problems getting SBCL to build, and I see other packages like GHC
> and SML (although I haven't looked at those in quite some time) have
> similar bootstrapping problems.  I think my solution for SBCL might be
> good to generalize, but I'm not sure of all the issues that might come
> up, or the ones that would suddenly appear.

Sorry, your solution is bad to generalize. The way you did restricts
pkgsrc usability on other platforms and even on NetBSD itself, since you
provided only i386 bootstrap package, while I successfully build and use
pkgsrc-built SBCL on FreeBSD as well.

> So I ended up making a directory on ftp.nb.o for prebuilt SBCL packages.
> there is a directory tree for $MACHINE_ARCH and $OS_VERSION.  SBCL
> then grabs one of those packages and untars it in $WRKDIR to get the
> tools to build the package.

It doesn't work that way after I updated the package. Your activity
periods are too rare, could you follow SBCL development more frequently?
Maybe quarterly for start?

BTW, SML/NJ doesn't have the problem you describe, Moscow ML and PolyML
don't have it at all not a sign of it.


Home | Main Index | Thread Index | Old Index