On 26 Jun 2009, at 23:06, Brendan Cully wrote:

> On Friday, 26 June 2009 at 21:49, Jean-François Mertens wrote:
>>
>> On 26 Jun 2009, at 20:48, Jean-François Mertens wrote:
>>
>>> But then I get another snag, lablgl-related (cf above) this time :
>>>> ocamlmktop -I +lablGL -thread  -o lablgtktop unix.cma threads.cma
>>>> lablgl.cma \
>>>>       -I . lablgtk.cma lablgtkgl.cma lablglade.cma  
>>>> lablgnomecanvas.cma
>>>> lablgnomeui.cma lablpanel.cma lablrsvg.cma lablgtkspell.cma
>>>> lablgtksourceview.cma gtkThread.cmo
>>>> File "_none_", line 1, characters 0-1:
>>>> Error: The file /sw/lib/ocaml/lablGL/lablgl.cma is not a bytecode
>>>> object file
>>
>> Rebuilding lablgl-x11 solved the problem.
>> Might deps of ocaml have to rebuilt
>> after the recent update ??
>
> Looks that way, yes. We should probably go with ocaml (=%v) or so.

including that some deps may have to be updated to a new version.
E.g., with current ocaml one needs %v=5.12 for camlp5 (with previous
ocaml, %v=5.11 was needed; in fink: %v=5.08).
It would be nice if such upgrades were in some way synchronised ..

But for now, Jesse : can I just commit my current camlp5 (cvs diff  
below) ?

JF Mertens

PS: cvs diff for camlp5 :

diff -r1.3 camlp5.info
7,8d6
<
< The current distributed version is 4.07 (released 2007-08-04).
10c8
< Version: 5.08
---
 > Version: 5.12
15,20c13,15
< Source-MD5: 61f617f11eedb26ad8607fe21413f920
< BuildDepends: fink (>= 0.24.12)
< Depends: ocaml (>= 3.08)
< PatchFile: %n.patch
< PatchFile-MD5: e4b069b0a06c0e297486264d8a653962
< PatchScript: sed 's|@PREFIX@|%p|g' < %{PatchFile} | patch -p1
---
 > Source-MD5: 28a86d4f1da8983b7fc773262fa52f1f
 > BuildDepends: fink (>= 0.24.12-1)
 > Depends: ocaml (>= 3.11.0-1)
22c17
<   ./configure
---
 >   ./configure --prefix %p --mandir %p/share/man


------------------------------------------------------------------------------
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to