Re: [racket-dev] [plt] Push #27511: master branch updated

2013-09-16 Thread Robby Findler
So you want scribble to generate a link that can, when clicked (or maybe
when the docs are built) turn into the real link or turn into "please
install package X"?

Robby

On Monday, September 16, 2013, Sam Tobin-Hochstadt wrote:

> I think the Typed Racket docs should have pointers to how to use other
> libraries in a typed fashion -- it's a question that comes up a lot.
>
> Sam
>
> On Mon, Sep 16, 2013 at 5:16 PM, Robby Findler
> > wrote:
> > Can that code not be moved into the relevant packages instead?
> >
> > Robby
> >
> >
> > On Mon, Sep 16, 2013 at 3:21 PM, Asumu Takikawa 
> > >
> wrote:
> >>
> >> On 2013-09-16 16:17:33 -0400, as...@racket-lang.org wrote:
> >> > +@defmodule[math #:no-declare #:link-target? #f]
> >> > +@defmodule[plot/typed #:no-declare #:link-target? #f]
> >>
> >> These two lines cause `raco setup` to complain with a warning about
> >> undeclared dependencies. It seems silly, though, to have the TR doc
> >> package force a dependency on `math`. Can I quelch the warning somehow?
> >> (like a "I don't really care if the dependency is missing" flag)
> >>
> >> Cheers,
> >> Asumu
> >> _
> >>   Racket Developers list:
> >>   http://lists.racket-lang.org/dev
> >
> >
> >
> > _
> >   Racket Developers list:
> >   http://lists.racket-lang.org/dev
> >
>
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] [plt] Push #27511: master branch updated

2013-09-16 Thread Sam Tobin-Hochstadt
I think the Typed Racket docs should have pointers to how to use other
libraries in a typed fashion -- it's a question that comes up a lot.

Sam

On Mon, Sep 16, 2013 at 5:16 PM, Robby Findler
 wrote:
> Can that code not be moved into the relevant packages instead?
>
> Robby
>
>
> On Mon, Sep 16, 2013 at 3:21 PM, Asumu Takikawa  wrote:
>>
>> On 2013-09-16 16:17:33 -0400, as...@racket-lang.org wrote:
>> > +@defmodule[math #:no-declare #:link-target? #f]
>> > +@defmodule[plot/typed #:no-declare #:link-target? #f]
>>
>> These two lines cause `raco setup` to complain with a warning about
>> undeclared dependencies. It seems silly, though, to have the TR doc
>> package force a dependency on `math`. Can I quelch the warning somehow?
>> (like a "I don't really care if the dependency is missing" flag)
>>
>> Cheers,
>> Asumu
>> _
>>   Racket Developers list:
>>   http://lists.racket-lang.org/dev
>
>
>
> _
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
>
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] [plt] Push #27511: master branch updated

2013-09-16 Thread Sam Tobin-Hochstadt
I think what Carl suggested is preferable -- a link that only exists
if the package it links to exists.  Alternatively, a link that goes to
the web if the package doesn't exist yet.  I think the latter is
planned but not yet implemented, from my recollection.

Sam

On Mon, Sep 16, 2013 at 5:41 PM, Robby Findler
 wrote:
> So you want scribble to generate a link that can, when clicked (or maybe
> when the docs are built) turn into the real link or turn into "please
> install package X"?
>
> Robby
>
>
> On Monday, September 16, 2013, Sam Tobin-Hochstadt wrote:
>>
>> I think the Typed Racket docs should have pointers to how to use other
>> libraries in a typed fashion -- it's a question that comes up a lot.
>>
>> Sam
>>
>> On Mon, Sep 16, 2013 at 5:16 PM, Robby Findler
>>  wrote:
>> > Can that code not be moved into the relevant packages instead?
>> >
>> > Robby
>> >
>> >
>> > On Mon, Sep 16, 2013 at 3:21 PM, Asumu Takikawa 
>> > wrote:
>> >>
>> >> On 2013-09-16 16:17:33 -0400, as...@racket-lang.org wrote:
>> >> > +@defmodule[math #:no-declare #:link-target? #f]
>> >> > +@defmodule[plot/typed #:no-declare #:link-target? #f]
>> >>
>> >> These two lines cause `raco setup` to complain with a warning about
>> >> undeclared dependencies. It seems silly, though, to have the TR doc
>> >> package force a dependency on `math`. Can I quelch the warning somehow?
>> >> (like a "I don't really care if the dependency is missing" flag)
>> >>
>> >> Cheers,
>> >> Asumu
>> >> _
>> >>   Racket Developers list:
>> >>   http://lists.racket-lang.org/dev
>> >
>> >
>> >
>> > _
>> >   Racket Developers list:
>> >   http://lists.racket-lang.org/dev
>> >
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] [plt] Push #27511: master branch updated

2013-09-16 Thread Matthew Flatt
It's implemented, but it's not currently an option for `defmodule`.
I'll look into adding the option.

At Mon, 16 Sep 2013 17:49:27 -0400, Sam Tobin-Hochstadt wrote:
> I think what Carl suggested is preferable -- a link that only exists
> if the package it links to exists.  Alternatively, a link that goes to
> the web if the package doesn't exist yet.  I think the latter is
> planned but not yet implemented, from my recollection.
> 
> Sam
> 
> On Mon, Sep 16, 2013 at 5:41 PM, Robby Findler
>  wrote:
> > So you want scribble to generate a link that can, when clicked (or maybe
> > when the docs are built) turn into the real link or turn into "please
> > install package X"?
> >
> > Robby
> >
> >
> > On Monday, September 16, 2013, Sam Tobin-Hochstadt wrote:
> >>
> >> I think the Typed Racket docs should have pointers to how to use other
> >> libraries in a typed fashion -- it's a question that comes up a lot.
> >>
> >> Sam
> >>
> >> On Mon, Sep 16, 2013 at 5:16 PM, Robby Findler
> >>  wrote:
> >> > Can that code not be moved into the relevant packages instead?
> >> >
> >> > Robby
> >> >
> >> >
> >> > On Mon, Sep 16, 2013 at 3:21 PM, Asumu Takikawa 
> >> > wrote:
> >> >>
> >> >> On 2013-09-16 16:17:33 -0400, as...@racket-lang.org wrote:
> >> >> > +@defmodule[math #:no-declare #:link-target? #f]
> >> >> > +@defmodule[plot/typed #:no-declare #:link-target? #f]
> >> >>
> >> >> These two lines cause `raco setup` to complain with a warning about
> >> >> undeclared dependencies. It seems silly, though, to have the TR doc
> >> >> package force a dependency on `math`. Can I quelch the warning somehow?
> >> >> (like a "I don't really care if the dependency is missing" flag)
> >> >>
> >> >> Cheers,
> >> >> Asumu
> >> >> _
> >> >>   Racket Developers list:
> >> >>   http://lists.racket-lang.org/dev
> >> >
> >> >
> >> >
> >> > _
> >> >   Racket Developers list:
> >> >   http://lists.racket-lang.org/dev
> >> >
> _
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] [plt] Push #27511: master branch updated

2013-09-16 Thread Carl Eastlund
Perhaps some macro hackery on the defmodule form to make it into
defmodule-if-exists and only document that the module is typed if it is
actually installed?

Carl Eastlund


On Mon, Sep 16, 2013 at 4:21 PM, Asumu Takikawa  wrote:

> On 2013-09-16 16:17:33 -0400, as...@racket-lang.org wrote:
> > +@defmodule[math #:no-declare #:link-target? #f]
> > +@defmodule[plot/typed #:no-declare #:link-target? #f]
>
> These two lines cause `raco setup` to complain with a warning about
> undeclared dependencies. It seems silly, though, to have the TR doc
> package force a dependency on `math`. Can I quelch the warning somehow?
> (like a "I don't really care if the dependency is missing" flag)
>
> Cheers,
> Asumu
> _
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
>
>
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] [plt] Push #27511: master branch updated

2013-09-16 Thread Robby Findler
Can that code not be moved into the relevant packages instead?

Robby


On Mon, Sep 16, 2013 at 3:21 PM, Asumu Takikawa  wrote:

> On 2013-09-16 16:17:33 -0400, as...@racket-lang.org wrote:
> > +@defmodule[math #:no-declare #:link-target? #f]
> > +@defmodule[plot/typed #:no-declare #:link-target? #f]
>
> These two lines cause `raco setup` to complain with a warning about
> undeclared dependencies. It seems silly, though, to have the TR doc
> package force a dependency on `math`. Can I quelch the warning somehow?
> (like a "I don't really care if the dependency is missing" flag)
>
> Cheers,
> Asumu
> _
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
>
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] [plt] Push #26693: master branch updated

2013-09-16 Thread Greg Hendershott
After I saw this, I closed the open pull request over on GitHub:

https://github.com/plt/racket/pull/324

BTW here is the commit over on GitHub:

https://github.com/plt/racket/commit/c6e28435578b6b8607d4c767ee956f88c8388ff0

I fetched from HEAD at the time, verison 5.3.4.7.  I've been using it
on that server ever since.

Today I wanted to move my app to a new server, which has 5.3.6
official. I was really confused that I got an error because
imap-append has only 3 args not 4. My PR added the 4th, optional arg.

Did this not get merged into release, after all??

Maybe I'm doing something really dumb, but...?


p.s. I do see my changes as the last commit in collect/net/imap.rkt

https://github.com/plt/racket/commits/c6e28435578b6b8607d4c767ee956f88c8388ff0/collects/net/imap.rkt

and the scribbling collects/net/scribblings/imap.scrbl

https://github.com/plt/racket/blob/c6e28435578b6b8607d4c767ee956f88c8388ff0/collects/net/scribblings/imap.scrbl

This should have been in 5.3.5, as well as 5.3.6. But it doesn't seem
to be in either (I just tried both).


p.p.s. Post package split, I'm not sure how to follow the history. But
searching for "imap-append":

https://github.com/plt/racket/search?q=imap-append&source=c

I do see my changes in pkgs/net-lib/net/imap.rkt

https://github.com/plt/racket/blob/3ad009070e063614f22a32fbbffa950a8d84e599/pkgs/net-lib/net/imap.rkt#L21-L25
https://github.com/plt/racket/blob/3ad009070e063614f22a32fbbffa950a8d84e599/pkgs/net-lib/net/imap.rkt#L21-L25

and in the scribbling:

https://github.com/plt/racket/blob/3ad009070e063614f22a32fbbffa950a8d84e599/pkgs/net-lib/net/imap.rkt#L21-L25

But I get a similar error running 5.900.


On Tue, Apr 23, 2013 at 5:50 PM,   wrote:
> mflatt has updated `master' from 8c7632c025 to c6e2843557.
>   http://git.racket-lang.org/plt/8c7632c025..c6e2843557
>
> =[ 2 Commits ]==
> Directory summary:
>   19.8% collects/net/scribblings/
>   49.1% collects/net/
>9.1% collects/racket/private/
>   21.8% src/racket/src/
>
> ~~
>
> 3779cf6 Matthew Flatt  2013-04-23 15:06
> :
> | fix `exn:fail:filesystem:missing-module-path'
> :
>   M collects/racket/private/kernstruct.rkt | 2 +-
>   M src/racket/src/makeexn | 2 +-
>   M src/racket/src/schexn.h| 2 +-
>   M src/racket/src/schvers.h   | 4 ++--
>
> ~~
>
> c6e2843 Greg Hendershott  2013-04-23 13:50
> :
> | Add optional message flags argument to imap-append.
> |
> | Previously this was hard-coded to use the \Seen flag. Now that's the
> | default value when the argument is not supplied.
> :
>   M collects/net/imap.rkt   | 20 +---
>   M collects/net/scribblings/imap.scrbl |  5 -
>
> =[ Overall Diff ]===
>
> collects/net/imap.rkt
> ~
> --- OLD/collects/net/imap.rkt
> +++ NEW/collects/net/imap.rkt
> @@ -1,8 +1,9 @@
>  #lang racket/base
>
> -(require racket/contract/base
> - racket/tcp
> - openssl
> +(require racket/contract/base
> + racket/tcp
> + openssl
> + racket/format
>   "private/rbtree.rkt")
>
>  ;; define the imap struct and its predicate here, for use in the contract, 
> below
> @@ -16,7 +17,12 @@
>   [imap-list-child-mailboxes
>(->* (imap-connection? (or/c string? bytes? #f))
> ((or/c string? bytes?))
> -   (listof (list/c (listof symbol?) bytes?)))])
> +   (listof (list/c (listof symbol?) bytes?)))]
> + [imap-append ((imap? string? (or/c string? bytes?))
> +   ((listof
> + (or/c 'seen 'answered 'flagged 'deleted 'draft 'recent)))
> +  . ->* .
> +  void?)])
>
>  (provide
>   imap-connection?
> @@ -45,7 +51,7 @@
>   imap-pending-updates?
>
>   imap-get-messages
> - imap-copy imap-append
> + imap-copy
>   imap-store imap-flag->symbol symbol->imap-flag
>   imap-expunge
>
> @@ -539,13 +545,13 @@
>(check-ok
> (imap-send imap (list "COPY" (box (msg-set msgs)) dest-mailbox) void)))
>
> -(define (imap-append imap dest-mailbox msg)
> +(define (imap-append imap dest-mailbox msg [flags '(seen)])
>(no-expunges 'imap-append imap)
>(let ([msg (if (bytes? msg) msg (string->bytes/utf-8 msg))])
>  (check-ok
>   (imap-send imap (list "APPEND"
> dest-mailbox
> -   (box "(\\Seen)")
> +   (box (~a (map symbol->imap-flag flags)))
> (box (format "{~a}" (bytes-length msg
>  void
>  (lambda (loop contin)
>
> collects/net/scribblings/imap.scrbl
> ~~~
> --- OLD/collects/net/scribblings/imap.scrbl
> +++ NEW/collects/net/scribblings/imap.scrbl
> @@ -416,7 +416,10 @@ Pending expunges must be handled before calling this 
> function; see
>
>  @defproc[(imap-append [imap imap-connection?]
>[mai

Re: [racket-dev] Racket should install libracket3m-X.Y.Z.so as libracket3m.so.X.Y.Z

2013-09-16 Thread Matthew Flatt
At Mon, 16 Sep 2013 18:10:34 +0200, Juan Francisco Cantero Hurtado wrote:
> On 09/11/13 10:42, Juan Francisco Cantero Hurtado wrote:
> > The standard on modern unix systems is to name the shared libraries with
> > this pattern: "lib" + name + ".so." + major version + "." + minor
> > version. Racket uses libracket-5.3.6.so. It isn't correct.
> >
> > -rwxr-xr-x  1 root  wheel   9.0M Aug 17 04:28
> > /usr/local/lib/libracket3m-5.3.6.so
> > -rw-r--r--  1 root  wheel  14.3M Aug 17 04:28 /usr/local/lib/libracket3m.a
> > -rw-r--r--  1 root  wheel   852B Aug 17 04:28 /usr/local/lib/libracket3m.la
> > lrwxr-xr-x  1 root  wheel20B Aug 17 05:51
> > /usr/local/lib/libracket3m.so -> libracket3m-5.3.6.so
> >
> > Look some examples. libpng on OpenBSD:
> >
> > lrwxr-xr-x  1 root  wheel10B Sep 10 19:30 /usr/local/lib/libpng.a ->
> > libpng16.a
> > -rw-r--r--  1 root  bin 720B Aug 17 02:22 /usr/local/lib/libpng.la
> > lrwxr-xr-x  1 root  wheel16B Sep 10 19:30
> > /usr/local/lib/libpng.so.17.0 -> libpng16.so.17.0
> > -rw-r--r--  1 root  bin 1.2M Aug 17 02:22 /usr/local/lib/libpng16.a
> > -rw-r--r--  1 root  bin 730B Aug 17 02:22 /usr/local/lib/libpng16.la
> > -rw-r--r--  1 root  bin 703K Aug 17 02:22
> > /usr/local/lib/libpng16.so.17.0
> >
> > libarchive on Gentoo:
> >
> > lrwxrwxrwx 1 root root 20 May 10 09:12 /usr/lib/libarchive.so ->
> > libarchive.so.13.1.2
> > lrwxrwxrwx 1 root root 20 May 10 09:12 /usr/lib/libarchive.so.13 ->
> > libarchive.so.13.1.2
> > -rwxr-xr-x 1 root root 723968 May 10 09:12 /usr/lib/libarchive.so.13.1.2
> >
> >
> > Also you should add some easy setting to change the suffix X.Y.Z of the
> > lib. Some projects use variables in configure or the main makefile. The
> > version of the libs is unrelated to the version of the software. On
> > OpenBSD we change the numbers, so we can control when the dependencies
> > require an update.
> >
> 
> Any comment about this?. Basically, I need to rename 
> libracket3m-5.3.6.so to libracket3m.so.0.0. I've searched where are the 
> version numbers in the makefiles and configure but I've not found it.

It's set via `configure`. See line 1408 in 

  racket/src/racket/configure.ac

which uses `-release ${plt_lib_version}`

We went with `-release` mode instead of version numbers, because we
didn't want to try to track of binary compatibility at the
shared-library level.

As you say, release versions don't necessarily have anything to do with
library versions, and it's almost certainly the case that libraries for
different v5.x releases cannot be substituted for each other (e.g., the
value of `scheme_char_string_type` is likely to shift). It would make
sense to simply introduce a new shared-library major version for every
release.

Overall, we haven't tried to provide shared-library versions mostly
because the libracket shared library doesn't seem all that useful. I'm
happy to accept patches to the `configure` script so that you can
configure the library name, though.

_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Installing subsets of Racket

2013-09-16 Thread Laurent
Sounds good!

I think as long as it's possible to somehow choose between byte-code and
source-code packages/distributions, there should not be too much to worry
about. My server would be very happy with byte-code packages, and my
desktop with a full source-code Racket.

Laurent


On Mon, Sep 16, 2013 at 5:04 PM, Jay McCarthy wrote:

> Hi Laurent,
>
> I think that the solution to this are "binary" builds versions of
> a package that only have the bytecode and documentation.
>
> We're a bit behind on binary builds, because when they were discussed
> for the main repository [1] they were rejected. I hope to be able to
> still provide them for ring-0 packages through the results of DrDr
> running tests (and thus compiling) on those packages, but it's in the
> future.
>
> The result would be that when you installed a package in "binary"
> form, you would only get the "deps" and not the "build-deps". (And
> you'd probably get those in binary form too.)
>
> Jay
>
> 1. http://www.mail-archive.com/dev@racket-lang.org/msg08879.html
>
> On Mon, Sep 16, 2013 at 2:32 AM, Laurent  wrote:
> > Hi,
> >
> > (this is not a complain, just an inquiry)
> >
> > While installing Racket on a small server, I wanted to avoid installing
> gui
> > and doc related libraries.
> > The minimal install was great!
> >
> > Then I wanted to install a package of my own (the aptly named "bazaar"),
> > which requires "images" and other gui libs (which I actually would not
> use
> > on the server), among other things, but no doc
> >
> > But the "images" package draws racket-doc and gui-doc dependencies,
> which in
> > turn draws practically all of Racket. And it then takes a much longer
> time
> > for `raco setup` to do its job that I had hoped for.
> >
> > Certainly, this can be resolved by splitting "images" and "bazaar" into
> lib,
> > gui and docs packages, but I foresee another problem:
> > It's difficult to enforce such a split for third-party libraries, as it
> puts
> > the burden on the user.
> > And the first package like that to be installed will again draw all of
> > Racket dependencies.
> >
> > This is probably not a trivial matter, but what can be done about this?
> >
> > My dream would be that gui and doc dependencies are never triggered,
> without
> > preventing the packages I actually use to be downloaded, but I don't know
> > how this could actually be ensured without a good amount of magic.
> >
> > Merely preventing downloads does not sound like a good option though.
> >
> > I bet you've already discussed this far and wide, so are there any plans?
> >
> > Laurent
> >
> > _
> >   Racket Developers list:
> >   http://lists.racket-lang.org/dev
> >
>
>
>
> --
> Jay McCarthy 
> Assistant Professor / Brigham Young University
> http://faculty.cs.byu.edu/~jay
>
> "The glory of God is Intelligence" - D&C 93
>
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Installing subsets of Racket

2013-09-16 Thread Laurent
great, thanks, that was quick!


On Mon, Sep 16, 2013 at 6:34 PM, Robby Findler
wrote:

> In the meantime, the images pkg is now broken up and images-lib depends
> only on draw-lib (and some unstable stuff), no longer on the full gui
> library or the docs.
>
> Robby
>
>
> On Mon, Sep 16, 2013 at 11:24 AM, Laurent wrote:
>
>> Sounds good!
>>
>> I think as long as it's possible to somehow choose between byte-code and
>> source-code packages/distributions, there should not be too much to worry
>> about. My server would be very happy with byte-code packages, and my
>> desktop with a full source-code Racket.
>>
>> Laurent
>>
>>
>>
>> On Mon, Sep 16, 2013 at 5:04 PM, Jay McCarthy wrote:
>>
>>> Hi Laurent,
>>>
>>> I think that the solution to this are "binary" builds versions of
>>> a package that only have the bytecode and documentation.
>>>
>>> We're a bit behind on binary builds, because when they were discussed
>>> for the main repository [1] they were rejected. I hope to be able to
>>> still provide them for ring-0 packages through the results of DrDr
>>> running tests (and thus compiling) on those packages, but it's in the
>>> future.
>>>
>>> The result would be that when you installed a package in "binary"
>>> form, you would only get the "deps" and not the "build-deps". (And
>>> you'd probably get those in binary form too.)
>>>
>>> Jay
>>>
>>> 1. http://www.mail-archive.com/dev@racket-lang.org/msg08879.html
>>>
>>> On Mon, Sep 16, 2013 at 2:32 AM, Laurent 
>>> wrote:
>>> > Hi,
>>> >
>>> > (this is not a complain, just an inquiry)
>>> >
>>> > While installing Racket on a small server, I wanted to avoid
>>> installing gui
>>> > and doc related libraries.
>>> > The minimal install was great!
>>> >
>>> > Then I wanted to install a package of my own (the aptly named
>>> "bazaar"),
>>> > which requires "images" and other gui libs (which I actually would not
>>> use
>>> > on the server), among other things, but no doc
>>> >
>>> > But the "images" package draws racket-doc and gui-doc dependencies,
>>> which in
>>> > turn draws practically all of Racket. And it then takes a much longer
>>> time
>>> > for `raco setup` to do its job that I had hoped for.
>>> >
>>> > Certainly, this can be resolved by splitting "images" and "bazaar"
>>> into lib,
>>> > gui and docs packages, but I foresee another problem:
>>> > It's difficult to enforce such a split for third-party libraries, as
>>> it puts
>>> > the burden on the user.
>>> > And the first package like that to be installed will again draw all of
>>> > Racket dependencies.
>>> >
>>> > This is probably not a trivial matter, but what can be done about this?
>>> >
>>> > My dream would be that gui and doc dependencies are never triggered,
>>> without
>>> > preventing the packages I actually use to be downloaded, but I don't
>>> know
>>> > how this could actually be ensured without a good amount of magic.
>>> >
>>> > Merely preventing downloads does not sound like a good option though.
>>> >
>>> > I bet you've already discussed this far and wide, so are there any
>>> plans?
>>> >
>>> > Laurent
>>> >
>>> > _
>>> >   Racket Developers list:
>>> >   http://lists.racket-lang.org/dev
>>> >
>>>
>>>
>>>
>>> --
>>> Jay McCarthy 
>>> Assistant Professor / Brigham Young University
>>> http://faculty.cs.byu.edu/~jay
>>>
>>> "The glory of God is Intelligence" - D&C 93
>>>
>>
>>
>> _
>>   Racket Developers list:
>>   http://lists.racket-lang.org/dev
>>
>>
>
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Installing subsets of Racket

2013-09-16 Thread Robby Findler
In the meantime, the images pkg is now broken up and images-lib depends
only on draw-lib (and some unstable stuff), no longer on the full gui
library or the docs.

Robby


On Mon, Sep 16, 2013 at 11:24 AM, Laurent  wrote:

> Sounds good!
>
> I think as long as it's possible to somehow choose between byte-code and
> source-code packages/distributions, there should not be too much to worry
> about. My server would be very happy with byte-code packages, and my
> desktop with a full source-code Racket.
>
> Laurent
>
>
>
> On Mon, Sep 16, 2013 at 5:04 PM, Jay McCarthy wrote:
>
>> Hi Laurent,
>>
>> I think that the solution to this are "binary" builds versions of
>> a package that only have the bytecode and documentation.
>>
>> We're a bit behind on binary builds, because when they were discussed
>> for the main repository [1] they were rejected. I hope to be able to
>> still provide them for ring-0 packages through the results of DrDr
>> running tests (and thus compiling) on those packages, but it's in the
>> future.
>>
>> The result would be that when you installed a package in "binary"
>> form, you would only get the "deps" and not the "build-deps". (And
>> you'd probably get those in binary form too.)
>>
>> Jay
>>
>> 1. http://www.mail-archive.com/dev@racket-lang.org/msg08879.html
>>
>> On Mon, Sep 16, 2013 at 2:32 AM, Laurent 
>> wrote:
>> > Hi,
>> >
>> > (this is not a complain, just an inquiry)
>> >
>> > While installing Racket on a small server, I wanted to avoid installing
>> gui
>> > and doc related libraries.
>> > The minimal install was great!
>> >
>> > Then I wanted to install a package of my own (the aptly named "bazaar"),
>> > which requires "images" and other gui libs (which I actually would not
>> use
>> > on the server), among other things, but no doc
>> >
>> > But the "images" package draws racket-doc and gui-doc dependencies,
>> which in
>> > turn draws practically all of Racket. And it then takes a much longer
>> time
>> > for `raco setup` to do its job that I had hoped for.
>> >
>> > Certainly, this can be resolved by splitting "images" and "bazaar" into
>> lib,
>> > gui and docs packages, but I foresee another problem:
>> > It's difficult to enforce such a split for third-party libraries, as it
>> puts
>> > the burden on the user.
>> > And the first package like that to be installed will again draw all of
>> > Racket dependencies.
>> >
>> > This is probably not a trivial matter, but what can be done about this?
>> >
>> > My dream would be that gui and doc dependencies are never triggered,
>> without
>> > preventing the packages I actually use to be downloaded, but I don't
>> know
>> > how this could actually be ensured without a good amount of magic.
>> >
>> > Merely preventing downloads does not sound like a good option though.
>> >
>> > I bet you've already discussed this far and wide, so are there any
>> plans?
>> >
>> > Laurent
>> >
>> > _
>> >   Racket Developers list:
>> >   http://lists.racket-lang.org/dev
>> >
>>
>>
>>
>> --
>> Jay McCarthy 
>> Assistant Professor / Brigham Young University
>> http://faculty.cs.byu.edu/~jay
>>
>> "The glory of God is Intelligence" - D&C 93
>>
>
>
> _
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
>
>
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Racket should install libracket3m-X.Y.Z.so as libracket3m.so.X.Y.Z

2013-09-16 Thread Juan Francisco Cantero Hurtado

On 09/11/13 10:42, Juan Francisco Cantero Hurtado wrote:

The standard on modern unix systems is to name the shared libraries with
this pattern: "lib" + name + ".so." + major version + "." + minor
version. Racket uses libracket-5.3.6.so. It isn't correct.

-rwxr-xr-x  1 root  wheel   9.0M Aug 17 04:28
/usr/local/lib/libracket3m-5.3.6.so
-rw-r--r--  1 root  wheel  14.3M Aug 17 04:28 /usr/local/lib/libracket3m.a
-rw-r--r--  1 root  wheel   852B Aug 17 04:28 /usr/local/lib/libracket3m.la
lrwxr-xr-x  1 root  wheel20B Aug 17 05:51
/usr/local/lib/libracket3m.so -> libracket3m-5.3.6.so

Look some examples. libpng on OpenBSD:

lrwxr-xr-x  1 root  wheel10B Sep 10 19:30 /usr/local/lib/libpng.a ->
libpng16.a
-rw-r--r--  1 root  bin 720B Aug 17 02:22 /usr/local/lib/libpng.la
lrwxr-xr-x  1 root  wheel16B Sep 10 19:30
/usr/local/lib/libpng.so.17.0 -> libpng16.so.17.0
-rw-r--r--  1 root  bin 1.2M Aug 17 02:22 /usr/local/lib/libpng16.a
-rw-r--r--  1 root  bin 730B Aug 17 02:22 /usr/local/lib/libpng16.la
-rw-r--r--  1 root  bin 703K Aug 17 02:22
/usr/local/lib/libpng16.so.17.0

libarchive on Gentoo:

lrwxrwxrwx 1 root root 20 May 10 09:12 /usr/lib/libarchive.so ->
libarchive.so.13.1.2
lrwxrwxrwx 1 root root 20 May 10 09:12 /usr/lib/libarchive.so.13 ->
libarchive.so.13.1.2
-rwxr-xr-x 1 root root 723968 May 10 09:12 /usr/lib/libarchive.so.13.1.2


Also you should add some easy setting to change the suffix X.Y.Z of the
lib. Some projects use variables in configure or the main makefile. The
version of the libs is unrelated to the version of the software. On
OpenBSD we change the numbers, so we can control when the dependencies
require an update.



Any comment about this?. Basically, I need to rename 
libracket3m-5.3.6.so to libracket3m.so.0.0. I've searched where are the 
version numbers in the makefiles and configure but I've not found it.



_
 Racket Developers list:
 http://lists.racket-lang.org/dev


Re: [racket-dev] Racket should install libracket3m-X.Y.Z.so as libracket3m.so.X.Y.Z

2013-09-16 Thread Juan Francisco Cantero Hurtado

On 09/16/13 18:24, Matthew Flatt wrote:

At Mon, 16 Sep 2013 18:10:34 +0200, Juan Francisco Cantero Hurtado wrote:

On 09/11/13 10:42, Juan Francisco Cantero Hurtado wrote:

The standard on modern unix systems is to name the shared libraries with
this pattern: "lib" + name + ".so." + major version + "." + minor
version. Racket uses libracket-5.3.6.so. It isn't correct.

-rwxr-xr-x  1 root  wheel   9.0M Aug 17 04:28
/usr/local/lib/libracket3m-5.3.6.so
-rw-r--r--  1 root  wheel  14.3M Aug 17 04:28 /usr/local/lib/libracket3m.a
-rw-r--r--  1 root  wheel   852B Aug 17 04:28 /usr/local/lib/libracket3m.la
lrwxr-xr-x  1 root  wheel20B Aug 17 05:51
/usr/local/lib/libracket3m.so -> libracket3m-5.3.6.so

Look some examples. libpng on OpenBSD:

lrwxr-xr-x  1 root  wheel10B Sep 10 19:30 /usr/local/lib/libpng.a ->
libpng16.a
-rw-r--r--  1 root  bin 720B Aug 17 02:22 /usr/local/lib/libpng.la
lrwxr-xr-x  1 root  wheel16B Sep 10 19:30
/usr/local/lib/libpng.so.17.0 -> libpng16.so.17.0
-rw-r--r--  1 root  bin 1.2M Aug 17 02:22 /usr/local/lib/libpng16.a
-rw-r--r--  1 root  bin 730B Aug 17 02:22 /usr/local/lib/libpng16.la
-rw-r--r--  1 root  bin 703K Aug 17 02:22
/usr/local/lib/libpng16.so.17.0

libarchive on Gentoo:

lrwxrwxrwx 1 root root 20 May 10 09:12 /usr/lib/libarchive.so ->
libarchive.so.13.1.2
lrwxrwxrwx 1 root root 20 May 10 09:12 /usr/lib/libarchive.so.13 ->
libarchive.so.13.1.2
-rwxr-xr-x 1 root root 723968 May 10 09:12 /usr/lib/libarchive.so.13.1.2


Also you should add some easy setting to change the suffix X.Y.Z of the
lib. Some projects use variables in configure or the main makefile. The
version of the libs is unrelated to the version of the software. On
OpenBSD we change the numbers, so we can control when the dependencies
require an update.



Any comment about this?. Basically, I need to rename
libracket3m-5.3.6.so to libracket3m.so.0.0. I've searched where are the
version numbers in the makefiles and configure but I've not found it.


It's set via `configure`. See line 1408 in

   racket/src/racket/configure.ac

which uses `-release ${plt_lib_version}`


Oh. I was looking for the wrong string.  Thanks a lot!



We went with `-release` mode instead of version numbers, because we
didn't want to try to track of binary compatibility at the
shared-library level.

As you say, release versions don't necessarily have anything to do with
library versions, and it's almost certainly the case that libraries for
different v5.x releases cannot be substituted for each other (e.g., the
value of `scheme_char_string_type` is likely to shift). It would make
sense to simply introduce a new shared-library major version for every
release.

Overall, we haven't tried to provide shared-library versions mostly
because the libracket shared library doesn't seem all that useful. I'm
happy to accept patches to the `configure` script so that you can
configure the library name, though.


If I manage to fix the problem with the lib, I'll add a new option to 
configure to select the behavior of libtool.





_
 Racket Developers list:
 http://lists.racket-lang.org/dev


Re: [racket-dev] racket segfaults during raco setup on OpenBSD

2013-09-16 Thread Juan Francisco Cantero Hurtado

On 09/16/13 17:10, Matthew Flatt wrote:

I think this is a libffi problem, and I guess there's a patch that we
still need to add to the Racket copy of libffi (although I sync'd with
the latest libffi sson after the last time this was discussed).


I've created a pull request with the patch.



While we sort that out, you should be able to install the
"devel/libffi" package, then re-running `configure` should pick up the
installed libffi instead of building, and then things should work.


See also

  http://lists.racket-lang.org/users/archive/2013-April/057056.html

but skip to the end.


At Mon, 16 Sep 2013 10:58:13 -0400, Philippe Meunier wrote:

Hello,

Starting from a clean clone of the git repository, racket3m segfaults
on OpenBSD 5.3 while in the middle of doing the raco setup:

$ pwd
/home/meunier/lang/plt
$ make
[...]
Adding xrepl-test* as pkgs/xrepl-pkgs/xrepl-test
Writing racket/etc/config.rktd
racket/bin/racket -N raco -l- raco setup
raco setup: version: 5.90.0.9 [3m]
raco setup: installation name: development
raco setup: variants: 3m
raco setup: main collects: /home/meunier/lang/plt/racket/collects
[...]
raco setup: making: /drracket/gui-debugger
raco setup:  in /drracket/gui-debugger
Seg fault (internal error) at 0xa866246
*** Signal SIGABRT in . (Makefile:53 'plain-in-place')
*** Error 1 in /home/meunier/lang/plt (Makefile:41 'in-place')

GDB gives:

$ gdb racket/bin/racket racket.core
[...]
(gdb) bt
#0  0x0341bc2d in kill () at :2
#1  0x03487826 in raise (s=6) at /usr/src/lib/libc/gen/raise.c:39
#2  0x0348774c in abort () at /usr/src/lib/libc/stdlib/abort.c:70
#3  0x1c1fb8b5 in fault_handler ()
#4  
#5  0x0a866246 in sse2_composite_over_n_8_ () from
/usr/X11R6/lib/libpixman-1.so.28.0
#6  0x0a844c41 in pixman_composite_glyphs_no_mask () from
/usr/X11R6/lib/libpixman-1.so.28.0
#7  0x1001bb48 in composite_glyphs () from /usr/local/lib/libcairo.so.12.1
#8  0x10064978 in composite_glyphs () from /usr/local/lib/libcairo.so.12.1
#9  0x100662ea in clip_and_composite () from /usr/local/lib/libcairo.so.12.1
#10 0x100665b3 in _cairo_traps_compositor_glyphs () from
/usr/local/lib/libcairo.so.12.1
#11 0x1000da12 in _cairo_compositor_glyphs () from
/usr/local/lib/libcairo.so.12.1
#12 0x1001fed5 in _cairo_image_surface_glyphs () from
/usr/local/lib/libcairo.so.12.1
#13 0x100551d2 in _cairo_surface_show_text_glyphs () from
/usr/local/lib/libcairo.so.12.1
#14 0x100164ca in _cairo_gstate_show_text_glyphs () from
/usr/local/lib/libcairo.so.12.1
#15 0x1000727e in cairo_show_glyphs () from /usr/local/lib/libcairo.so.12.1
#16 0x0846b419 in pango_cairo_renderer_show_text_glyphs () from
/usr/local/lib/libpangocairo-1.0.so.3200.0
#17 0x0846b815 in pango_cairo_renderer_draw_glyphs () from
/usr/local/lib/libpangocairo-1.0.so.3200.0
#18 0x0ea2204a in pango_renderer_draw_glyphs () from
/usr/local/lib/libpango-1.0.so.3200.0
#19 0x0ea2215d in pango_renderer_draw_glyph_item () from
/usr/local/lib/libpango-1.0.so.3200.0
#20 0x0ea2280a in pango_renderer_draw_layout_line () from
/usr/local/lib/libpango-1.0.so.3200.0
#21 0x0846a028 in _pango_cairo_do_layout_line () from
/usr/local/lib/libpangocairo-1.0.so.3200.0
#22 0x08090d73 in ffi_call_SYSV () from /usr/local/lib/libffi.so.0.0
#23 0x08090b7a in ffi_call (cif=0x7e8134a0, fn=0x7d415c20, rvalue=0xcfbe2cf0,
avalue=0xcfbe2cb0) at src/x86/ffi.c:326
#24 0x1c1eeb8a in do_ptr_finalizer ()
#25 0x1c1eedb1 in do_ptr_finalizer ()
#26 0x033243f2 in ?? ()
#27 0x0002 in ?? ()
#28 0x81610754 in ?? ()
#29 0x89d764a0 in ?? ()
#30 0xcfbe2d98 in ?? ()
#31 0x0c4e30ef in ?? ()
#32 0x8162dc30 in ?? ()
#33 0x0c4e4074 in ?? ()
#34 0x in ?? ()
(gdb)




_
 Racket Developers list:
 http://lists.racket-lang.org/dev


Re: [racket-dev] [plt] Push #27511: master branch updated

2013-09-16 Thread Asumu Takikawa
On 2013-09-16 16:17:33 -0400, as...@racket-lang.org wrote:
> +@defmodule[math #:no-declare #:link-target? #f]
> +@defmodule[plot/typed #:no-declare #:link-target? #f]

These two lines cause `raco setup` to complain with a warning about
undeclared dependencies. It seems silly, though, to have the TR doc
package force a dependency on `math`. Can I quelch the warning somehow?
(like a "I don't really care if the dependency is missing" flag)

Cheers,
Asumu
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] racket segfaults during raco setup on OpenBSD

2013-09-16 Thread Matthew Flatt
Thanks! The pull request is now merged.

At Mon, 16 Sep 2013 17:59:16 +0200, Juan Francisco Cantero Hurtado wrote:
> On 09/16/13 17:10, Matthew Flatt wrote:
> > I think this is a libffi problem, and I guess there's a patch that we
> > still need to add to the Racket copy of libffi (although I sync'd with
> > the latest libffi sson after the last time this was discussed).
> 
> I've created a pull request with the patch.
> 
> >
> > While we sort that out, you should be able to install the
> > "devel/libffi" package, then re-running `configure` should pick up the
> > installed libffi instead of building, and then things should work.
> >
> >
> > See also
> >
> >   http://lists.racket-lang.org/users/archive/2013-April/057056.html
> >
> > but skip to the end.
> >
> >
> > At Mon, 16 Sep 2013 10:58:13 -0400, Philippe Meunier wrote:
> >> Hello,
> >>
> >> Starting from a clean clone of the git repository, racket3m segfaults
> >> on OpenBSD 5.3 while in the middle of doing the raco setup:
> >>
> >> $ pwd
> >> /home/meunier/lang/plt
> >> $ make
> >> [...]
> >> Adding xrepl-test* as pkgs/xrepl-pkgs/xrepl-test
> >> Writing racket/etc/config.rktd
> >> racket/bin/racket -N raco -l- raco setup
> >> raco setup: version: 5.90.0.9 [3m]
> >> raco setup: installation name: development
> >> raco setup: variants: 3m
> >> raco setup: main collects: /home/meunier/lang/plt/racket/collects
> >> [...]
> >> raco setup: making: /drracket/gui-debugger
> >> raco setup:  in /drracket/gui-debugger
> >> Seg fault (internal error) at 0xa866246
> >> *** Signal SIGABRT in . (Makefile:53 'plain-in-place')
> >> *** Error 1 in /home/meunier/lang/plt (Makefile:41 'in-place')
> >>
> >> GDB gives:
> >>
> >> $ gdb racket/bin/racket racket.core
> >> [...]
> >> (gdb) bt
> >> #0  0x0341bc2d in kill () at :2
> >> #1  0x03487826 in raise (s=6) at /usr/src/lib/libc/gen/raise.c:39
> >> #2  0x0348774c in abort () at /usr/src/lib/libc/stdlib/abort.c:70
> >> #3  0x1c1fb8b5 in fault_handler ()
> >> #4  
> >> #5  0x0a866246 in sse2_composite_over_n_8_ () from
> >> /usr/X11R6/lib/libpixman-1.so.28.0
> >> #6  0x0a844c41 in pixman_composite_glyphs_no_mask () from
> >> /usr/X11R6/lib/libpixman-1.so.28.0
> >> #7  0x1001bb48 in composite_glyphs () from /usr/local/lib/libcairo.so.12.1
> >> #8  0x10064978 in composite_glyphs () from /usr/local/lib/libcairo.so.12.1
> >> #9  0x100662ea in clip_and_composite () from 
> >> /usr/local/lib/libcairo.so.12.1
> >> #10 0x100665b3 in _cairo_traps_compositor_glyphs () from
> >> /usr/local/lib/libcairo.so.12.1
> >> #11 0x1000da12 in _cairo_compositor_glyphs () from
> >> /usr/local/lib/libcairo.so.12.1
> >> #12 0x1001fed5 in _cairo_image_surface_glyphs () from
> >> /usr/local/lib/libcairo.so.12.1
> >> #13 0x100551d2 in _cairo_surface_show_text_glyphs () from
> >> /usr/local/lib/libcairo.so.12.1
> >> #14 0x100164ca in _cairo_gstate_show_text_glyphs () from
> >> /usr/local/lib/libcairo.so.12.1
> >> #15 0x1000727e in cairo_show_glyphs () from /usr/local/lib/libcairo.so.12.1
> >> #16 0x0846b419 in pango_cairo_renderer_show_text_glyphs () from
> >> /usr/local/lib/libpangocairo-1.0.so.3200.0
> >> #17 0x0846b815 in pango_cairo_renderer_draw_glyphs () from
> >> /usr/local/lib/libpangocairo-1.0.so.3200.0
> >> #18 0x0ea2204a in pango_renderer_draw_glyphs () from
> >> /usr/local/lib/libpango-1.0.so.3200.0
> >> #19 0x0ea2215d in pango_renderer_draw_glyph_item () from
> >> /usr/local/lib/libpango-1.0.so.3200.0
> >> #20 0x0ea2280a in pango_renderer_draw_layout_line () from
> >> /usr/local/lib/libpango-1.0.so.3200.0
> >> #21 0x0846a028 in _pango_cairo_do_layout_line () from
> >> /usr/local/lib/libpangocairo-1.0.so.3200.0
> >> #22 0x08090d73 in ffi_call_SYSV () from /usr/local/lib/libffi.so.0.0
> >> #23 0x08090b7a in ffi_call (cif=0x7e8134a0, fn=0x7d415c20, 
> rvalue=0xcfbe2cf0,
> >> avalue=0xcfbe2cb0) at src/x86/ffi.c:326
> >> #24 0x1c1eeb8a in do_ptr_finalizer ()
> >> #25 0x1c1eedb1 in do_ptr_finalizer ()
> >> #26 0x033243f2 in ?? ()
> >> #27 0x0002 in ?? ()
> >> #28 0x81610754 in ?? ()
> >> #29 0x89d764a0 in ?? ()
> >> #30 0xcfbe2d98 in ?? ()
> >> #31 0x0c4e30ef in ?? ()
> >> #32 0x8162dc30 in ?? ()
> >> #33 0x0c4e4074 in ?? ()
> >> #34 0x in ?? ()
> >> (gdb)
> >>
> 
> 
> _
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


[racket-dev] racket segfaults during raco setup on OpenBSD

2013-09-16 Thread Philippe Meunier
Hello,

Starting from a clean clone of the git repository, racket3m segfaults
on OpenBSD 5.3 while in the middle of doing the raco setup:

$ pwd
/home/meunier/lang/plt
$ make
[...]
Adding xrepl-test* as pkgs/xrepl-pkgs/xrepl-test
Writing racket/etc/config.rktd
racket/bin/racket -N raco -l- raco setup  
raco setup: version: 5.90.0.9 [3m]
raco setup: installation name: development
raco setup: variants: 3m
raco setup: main collects: /home/meunier/lang/plt/racket/collects
[...]
raco setup: making: /drracket/gui-debugger
raco setup:  in /drracket/gui-debugger
Seg fault (internal error) at 0xa866246
*** Signal SIGABRT in . (Makefile:53 'plain-in-place')
*** Error 1 in /home/meunier/lang/plt (Makefile:41 'in-place')

GDB gives:

$ gdb racket/bin/racket racket.core 
[...]
(gdb) bt
#0  0x0341bc2d in kill () at :2
#1  0x03487826 in raise (s=6) at /usr/src/lib/libc/gen/raise.c:39
#2  0x0348774c in abort () at /usr/src/lib/libc/stdlib/abort.c:70
#3  0x1c1fb8b5 in fault_handler ()
#4  
#5  0x0a866246 in sse2_composite_over_n_8_ () from 
/usr/X11R6/lib/libpixman-1.so.28.0
#6  0x0a844c41 in pixman_composite_glyphs_no_mask () from 
/usr/X11R6/lib/libpixman-1.so.28.0
#7  0x1001bb48 in composite_glyphs () from /usr/local/lib/libcairo.so.12.1
#8  0x10064978 in composite_glyphs () from /usr/local/lib/libcairo.so.12.1
#9  0x100662ea in clip_and_composite () from /usr/local/lib/libcairo.so.12.1
#10 0x100665b3 in _cairo_traps_compositor_glyphs () from 
/usr/local/lib/libcairo.so.12.1
#11 0x1000da12 in _cairo_compositor_glyphs () from 
/usr/local/lib/libcairo.so.12.1
#12 0x1001fed5 in _cairo_image_surface_glyphs () from 
/usr/local/lib/libcairo.so.12.1
#13 0x100551d2 in _cairo_surface_show_text_glyphs () from 
/usr/local/lib/libcairo.so.12.1
#14 0x100164ca in _cairo_gstate_show_text_glyphs () from 
/usr/local/lib/libcairo.so.12.1
#15 0x1000727e in cairo_show_glyphs () from /usr/local/lib/libcairo.so.12.1
#16 0x0846b419 in pango_cairo_renderer_show_text_glyphs () from 
/usr/local/lib/libpangocairo-1.0.so.3200.0
#17 0x0846b815 in pango_cairo_renderer_draw_glyphs () from 
/usr/local/lib/libpangocairo-1.0.so.3200.0
#18 0x0ea2204a in pango_renderer_draw_glyphs () from 
/usr/local/lib/libpango-1.0.so.3200.0
#19 0x0ea2215d in pango_renderer_draw_glyph_item () from 
/usr/local/lib/libpango-1.0.so.3200.0
#20 0x0ea2280a in pango_renderer_draw_layout_line () from 
/usr/local/lib/libpango-1.0.so.3200.0
#21 0x0846a028 in _pango_cairo_do_layout_line () from 
/usr/local/lib/libpangocairo-1.0.so.3200.0
#22 0x08090d73 in ffi_call_SYSV () from /usr/local/lib/libffi.so.0.0
#23 0x08090b7a in ffi_call (cif=0x7e8134a0, fn=0x7d415c20, rvalue=0xcfbe2cf0, 
avalue=0xcfbe2cb0) at src/x86/ffi.c:326
#24 0x1c1eeb8a in do_ptr_finalizer ()
#25 0x1c1eedb1 in do_ptr_finalizer ()
#26 0x033243f2 in ?? ()
#27 0x0002 in ?? ()
#28 0x81610754 in ?? ()
#29 0x89d764a0 in ?? ()
#30 0xcfbe2d98 in ?? ()
#31 0x0c4e30ef in ?? ()
#32 0x8162dc30 in ?? ()
#33 0x0c4e4074 in ?? ()
#34 0x in ?? ()
(gdb)

Philippe

_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] racket segfaults during raco setup on OpenBSD

2013-09-16 Thread Matthew Flatt
I think this is a libffi problem, and I guess there's a patch that we
still need to add to the Racket copy of libffi (although I sync'd with
the latest libffi sson after the last time this was discussed).

While we sort that out, you should be able to install the
"devel/libffi" package, then re-running `configure` should pick up the
installed libffi instead of building, and then things should work.


See also

 http://lists.racket-lang.org/users/archive/2013-April/057056.html

but skip to the end.


At Mon, 16 Sep 2013 10:58:13 -0400, Philippe Meunier wrote:
> Hello,
> 
> Starting from a clean clone of the git repository, racket3m segfaults
> on OpenBSD 5.3 while in the middle of doing the raco setup:
> 
> $ pwd
> /home/meunier/lang/plt
> $ make
> [...]
> Adding xrepl-test* as pkgs/xrepl-pkgs/xrepl-test
> Writing racket/etc/config.rktd
> racket/bin/racket -N raco -l- raco setup  
> raco setup: version: 5.90.0.9 [3m]
> raco setup: installation name: development
> raco setup: variants: 3m
> raco setup: main collects: /home/meunier/lang/plt/racket/collects
> [...]
> raco setup: making: /drracket/gui-debugger
> raco setup:  in /drracket/gui-debugger
> Seg fault (internal error) at 0xa866246
> *** Signal SIGABRT in . (Makefile:53 'plain-in-place')
> *** Error 1 in /home/meunier/lang/plt (Makefile:41 'in-place')
> 
> GDB gives:
> 
> $ gdb racket/bin/racket racket.core 
> [...]
> (gdb) bt
> #0  0x0341bc2d in kill () at :2
> #1  0x03487826 in raise (s=6) at /usr/src/lib/libc/gen/raise.c:39
> #2  0x0348774c in abort () at /usr/src/lib/libc/stdlib/abort.c:70
> #3  0x1c1fb8b5 in fault_handler ()
> #4  
> #5  0x0a866246 in sse2_composite_over_n_8_ () from 
> /usr/X11R6/lib/libpixman-1.so.28.0
> #6  0x0a844c41 in pixman_composite_glyphs_no_mask () from 
> /usr/X11R6/lib/libpixman-1.so.28.0
> #7  0x1001bb48 in composite_glyphs () from /usr/local/lib/libcairo.so.12.1
> #8  0x10064978 in composite_glyphs () from /usr/local/lib/libcairo.so.12.1
> #9  0x100662ea in clip_and_composite () from /usr/local/lib/libcairo.so.12.1
> #10 0x100665b3 in _cairo_traps_compositor_glyphs () from 
> /usr/local/lib/libcairo.so.12.1
> #11 0x1000da12 in _cairo_compositor_glyphs () from 
> /usr/local/lib/libcairo.so.12.1
> #12 0x1001fed5 in _cairo_image_surface_glyphs () from 
> /usr/local/lib/libcairo.so.12.1
> #13 0x100551d2 in _cairo_surface_show_text_glyphs () from 
> /usr/local/lib/libcairo.so.12.1
> #14 0x100164ca in _cairo_gstate_show_text_glyphs () from 
> /usr/local/lib/libcairo.so.12.1
> #15 0x1000727e in cairo_show_glyphs () from /usr/local/lib/libcairo.so.12.1
> #16 0x0846b419 in pango_cairo_renderer_show_text_glyphs () from 
> /usr/local/lib/libpangocairo-1.0.so.3200.0
> #17 0x0846b815 in pango_cairo_renderer_draw_glyphs () from 
> /usr/local/lib/libpangocairo-1.0.so.3200.0
> #18 0x0ea2204a in pango_renderer_draw_glyphs () from 
> /usr/local/lib/libpango-1.0.so.3200.0
> #19 0x0ea2215d in pango_renderer_draw_glyph_item () from 
> /usr/local/lib/libpango-1.0.so.3200.0
> #20 0x0ea2280a in pango_renderer_draw_layout_line () from 
> /usr/local/lib/libpango-1.0.so.3200.0
> #21 0x0846a028 in _pango_cairo_do_layout_line () from 
> /usr/local/lib/libpangocairo-1.0.so.3200.0
> #22 0x08090d73 in ffi_call_SYSV () from /usr/local/lib/libffi.so.0.0
> #23 0x08090b7a in ffi_call (cif=0x7e8134a0, fn=0x7d415c20, rvalue=0xcfbe2cf0, 
> avalue=0xcfbe2cb0) at src/x86/ffi.c:326
> #24 0x1c1eeb8a in do_ptr_finalizer ()
> #25 0x1c1eedb1 in do_ptr_finalizer ()
> #26 0x033243f2 in ?? ()
> #27 0x0002 in ?? ()
> #28 0x81610754 in ?? ()
> #29 0x89d764a0 in ?? ()
> #30 0xcfbe2d98 in ?? ()
> #31 0x0c4e30ef in ?? ()
> #32 0x8162dc30 in ?? ()
> #33 0x0c4e4074 in ?? ()
> #34 0x in ?? ()
> (gdb)
> 
> Philippe
> 
> _
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Installing subsets of Racket

2013-09-16 Thread Jay McCarthy
Hi Laurent,

I think that the solution to this are "binary" builds versions of
a package that only have the bytecode and documentation.

We're a bit behind on binary builds, because when they were discussed
for the main repository [1] they were rejected. I hope to be able to
still provide them for ring-0 packages through the results of DrDr
running tests (and thus compiling) on those packages, but it's in the
future.

The result would be that when you installed a package in "binary"
form, you would only get the "deps" and not the "build-deps". (And
you'd probably get those in binary form too.)

Jay

1. http://www.mail-archive.com/dev@racket-lang.org/msg08879.html

On Mon, Sep 16, 2013 at 2:32 AM, Laurent  wrote:
> Hi,
>
> (this is not a complain, just an inquiry)
>
> While installing Racket on a small server, I wanted to avoid installing gui
> and doc related libraries.
> The minimal install was great!
>
> Then I wanted to install a package of my own (the aptly named "bazaar"),
> which requires "images" and other gui libs (which I actually would not use
> on the server), among other things, but no doc
>
> But the "images" package draws racket-doc and gui-doc dependencies, which in
> turn draws practically all of Racket. And it then takes a much longer time
> for `raco setup` to do its job that I had hoped for.
>
> Certainly, this can be resolved by splitting "images" and "bazaar" into lib,
> gui and docs packages, but I foresee another problem:
> It's difficult to enforce such a split for third-party libraries, as it puts
> the burden on the user.
> And the first package like that to be installed will again draw all of
> Racket dependencies.
>
> This is probably not a trivial matter, but what can be done about this?
>
> My dream would be that gui and doc dependencies are never triggered, without
> preventing the packages I actually use to be downloaded, but I don't know
> how this could actually be ensured without a good amount of magic.
>
> Merely preventing downloads does not sound like a good option though.
>
> I bet you've already discussed this far and wide, so are there any plans?
>
> Laurent
>
> _
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
>



-- 
Jay McCarthy 
Assistant Professor / Brigham Young University
http://faculty.cs.byu.edu/~jay

"The glory of God is Intelligence" - D&C 93
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


Re: [racket-dev] Bug report not confirmed

2013-09-16 Thread Eli Barzilay
On Friday, Eli Barzilay wrote:
> 
> There was a permission problem with it, which is fixed now.
> Unfortunately, it looks like the contents of those messages are
> lost.

Actually, I just remembered that the bug emails are routed through
gmail, so there are copies of everything that was lost.  (Expect a
mini-flood of 6 messages...)

-- 
  ((lambda (x) (x x)) (lambda (x) (x x)))  Eli Barzilay:
http://barzilay.org/   Maze is Life!
_
  Racket Developers list:
  http://lists.racket-lang.org/dev


[racket-dev] Installing subsets of Racket

2013-09-16 Thread Laurent
Hi,

(this is not a complain, just an inquiry)

While installing Racket on a small server, I wanted to avoid installing gui
and doc related libraries.
The minimal install was great!

Then I wanted to install a package of my own (the aptly named "bazaar"),
which requires "images" and other gui libs (which I actually would not use
on the server), among other things, but no doc

But the "images" package draws racket-doc and gui-doc dependencies, which
in turn draws practically all of Racket. And it then takes a much longer
time for `raco setup` to do its job that I had hoped for.

Certainly, this can be resolved by splitting "images" and "bazaar" into
lib, gui and docs packages, but I foresee another problem:
It's difficult to enforce such a split for third-party libraries, as it
puts the burden on the user.
And the first package like that to be installed will again draw all of
Racket dependencies.

This is probably not a trivial matter, but what can be done about this?

My dream would be that gui and doc dependencies are never triggered,
without preventing the packages I actually use to be downloaded, but I
don't know how this could actually be ensured without a good amount of
magic.

Merely preventing downloads does not sound like a good option though.

I bet you've already discussed this far and wide, so are there any plans?

Laurent
_
  Racket Developers list:
  http://lists.racket-lang.org/dev