Re: OCaml 4?

[Brendan Fabeny]

On 11/7/13, Michael Grünewald  wrote:
> John Marino wrote:
>
>> I was thinking the holdup was on your end,[…]
>> Has the whole thing stalled?  11 months to get a PR through when the
>> submitter is responsive seems excessive to me, maybe somebody else
>> should take over the PR if bf@ is too busy.
>
> It looks like it is stalled. It would actually nice if someone else
> would take care of that PR[1] but before this, I certainly need to take
> care of removing this NO_STAGE flag.  It is probably unproblematic, I
> did not study this staging functionality yet.
>

The ball has been back in my court since Michael sent me his update
for 4.01.  I've some other updates to commit this weekend, and I'll
resume the test builds for this and the associated PRs on Sunday.
(Hopefully some of the blockers from last time have now been fixed.)

>   [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/173364
>
> BTW I am very comfortable with BSD Make but I am not aware of any list
> of problem reports or developments in the project or ports build system.
>  Where could I start?

On open PRs in the database you cite above (it is searchable), or
unsolved failures on the mailing lists (e.g. freebsd-ports or
freebsd-pkg-fallout)  that interest or affect you.  Some recent goals
or changes are mentioned on wiki.FreebSD.org (although this contains
some outdated material as well).  Some of unfinished short-term
objectives include converting ports to support staging and to compile
with clang on FreeBSD 10, and updating the Porter's handbook.

b.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: petsc-2.3.3.p0_7,1

[Brendan Fabeny]

On 10/20/13, Guillaume DOLLÉ  wrote:

> Would it possible to update Petsc to version 3.4.3 ?
> Create a new port for slepc-3.4.3 (extension for petsc) could be also nice.
>
> Thank in advance.

Yes, both are on my todo list, as soon as I finish some other pending updates.

b.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: lang/sbcl

[Brendan Fabeny]

On 10/9/13, Joseph Mingrone  wrote:
> Hi,
>
> After upgrading sbcl to 1.1.12, stumpwm no longer compiles.  I'm
> compiling stumpwm from the git repository, which hasn't changed in quite
> awhile.
>
> If there is anything I can test or any other information I can provide,
> please let me know.
>
> Joseph
>
> % gmake
> /usr/local/bin/sbcl --load ./make-image.lisp
> This is SBCL 1.1.12, an implementation of ANSI Common Lisp.
> More information about SBCL is available at .
>
> SBCL is free software, provided as is, with absolutely no warranty.
> It is mostly in the public domain; some portions are provided under
> BSD-style licenses.  See the CREDITS and COPYING files in the
> distribution for more information.
> WARNING:
>compiling # completed without its
> input file #P"/usr/local/lib/sbcl/sb-bsd-sockets/NEWS"
> WARNING:
>loading # completed without its
> input file #P"/usr/local/lib/sbcl/sb-bsd-sockets/NEWS"
> WARNING:
>compiling # completed without its
> input file #P"/usr/local/lib/sbcl/sb-bsd-sockets/TODO"
> WARNING:
>loading # completed without its
> input file #P"/usr/local/lib/sbcl/sb-bsd-sockets/TODO"
>
> debugger invoked on a ASDF/FIND-SYSTEM:MISSING-COMPONENT:
>   Component STUMPWM not found
>

Yes, lang/sbcl switched to a newer version of ASDF, which handles the
loading of modules differently.  I had hoped to patch the two
dependent ports that are now broken because of this as part of the
sbcl update, but I was coming under some pressure to update sbcl, and
I didn't have a lot of time. From my cursory look during the sbcl
update, I believe that this error can be fixed by patching the broken
dependent ports so that they issue a pathspec to the working directory
in the "require" statement in the Makefile, or by splitting eache of
the broken ports into two subports, one of which installs source code
in the system module directory, and another which subsequently
compiles it, as is done now for some of the cl-* ports.  I don't know
if there are other problems. When the ASDF port and other CL compilers
are updated to newer versions of ASDF, the broken ports will probably
not work with them, either.

Regards,
  b.


> Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
>
> restarts (invokable by number or by possibly-abbreviated name):
>   0: [RETRY   ] Retry EVAL of current toplevel form.
>   1: [CONTINUE] Ignore error and continue loading file
> "/usr/home/jrm/scm/stumpwm.git/./make-image.lisp".
>   2: [ABORT   ] Abort loading file
> "/usr/home/jrm/scm/stumpwm.git/./make-image.lisp".
>   3:Ignore runtime option --load "./make-image.lisp".
>   4:Skip rest of --eval and --load options.
>   5:Skip to toplevel READ/EVAL/PRINT loop.
>   6: [EXIT] Exit SBCL (calling #'EXIT, killing the process).
>
> ((:METHOD ASDF/OPERATE:OPERATE (SYMBOL T)) ASDF/LISP-ACTION:LOAD-OP STUMPWM)
> [fast-method]
> 0]
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"