About a minute ago, Robby Findler wrote:
> Won't said newbie's be even more confused to find that drracket
> doesn't work? Or am I missing something here?
If the builds use our own copy of libffi then that's one *less* reason
for it to not work.
> On Tue, Apr 12, 2011 at 6:43 AM, Eli Barzilay w
Won't said newbie's be even more confused to find that drracket
doesn't work? Or am I missing something here?
Robby
On Tue, Apr 12, 2011 at 6:43 AM, Eli Barzilay wrote:
> Two minutes ago, Sam Tobin-Hochstadt wrote:
>> On Tue, Apr 12, 2011 at 7:32 AM, Eli Barzilay wrote:
>> > Two days ago, Matth
Two minutes ago, Sam Tobin-Hochstadt wrote:
> On Tue, Apr 12, 2011 at 7:32 AM, Eli Barzilay wrote:
> > Two days ago, Matthew Flatt wrote:
> >> As of the latest in the git repo, when libffi is installed
> >> (including header files), then `configure' detects it and uses it,
> >> instead of building
On Tue, Apr 12, 2011 at 7:32 AM, Eli Barzilay wrote:
> Two days ago, Matthew Flatt wrote:
>> As of the latest in the git repo, when libffi is installed
>> (including header files), then `configure' detects it and uses it,
>> instead of building the copy of libffi that is included with the
>> Racke
Two days ago, Matthew Flatt wrote:
> As of the latest in the git repo, when libffi is installed
> (including header files), then `configure' detects it and uses it,
> instead of building the copy of libffi that is included with the
> Racket sources.
Does anyone see any problem with adding `--disab
As of the latest in the git repo, when libffi is installed (including
header files), then `configure' detects it and uses it, instead of
building the copy of libffi that is included with the Racket sources.
Hopefully this will just work, but watch out for new `configure'
problems.
___
6 matches
Mail list logo
