gs?

[Claes Wikstrom]

Ben Hyde writes:
 > 
 > Hi again -
 > 
 > I'm attempting to get gs to work now.  I followed the
 > direction for getting and building the unique tcl, and
 > moving the files into the gs directory tree.  The commands
 > given in that README seem to be wrong
 > 
 > <   cp tcl7.6/unix/libtcl7.6.a $CC_ROOT/libraries/gs/c_src/lib/
 > >   cp tcl7.6/unix/libtcl76.a $CC_ROOT/libraries/gs/c_src/lib/
 > 
 > <   cp tcl7.6/unix/tcl2c $CC_ROOT/lib/libraries/gs/lib/
 > >   cp tcl7.6/unix/tcl2c $CC_ROOT/libraries/gs/lib/
 > 
 > <   cp tk4.2/unix/libtk4.2.a $CC_ROOT/libraries/gs/c_src/lib/
 > >   cp tk4.2/unix/libtk42.a $CC_ROOT/libraries/gs/c_src/lib/
 > 
 > After building it (see: <http://zap.ml.org/tmp/gs.log>)
 > it just hangs.  Below is the result of using dbg:c on it
 > as it starts up.  This was the first time I'd used dbg so
 > I won't pretend to know what it means - but I think I'm 
 > missing something called "wrap."
 > 


Ok I just checked your build log and it didn't look to bright.
It is all our fault and we have allready apologized ourselves enough
over the pretty crappy makefiles in the first release ov Open
Source Erlang.

We're expecting to release a new version with clean Makefiles
in just a couple of days, hopefully on monday. !! Which supposedly
builds everything straight.

Building "gs" with the first release requires exactly the right
moves visavi picking up the patched version of tcl/tk, and copying the
5 right files to tye directory gs/c_src/lib

This was a bad move from our side and in the next release this
hazzle is removed. (Monday ..)

Now, for the .... trace ..

 > Thanks for your help. - ben
 > 
 > (z@REDACTED)1> l(gs).
 > {module,gs}
 > (z@REDACTED)2> dbg:c(gs, start, []).
 > (<0.34.0>) call erlang:whereis(code_server)
 > ...
 > (<0.41.0>) call erlang:db_put(12,{1,lives})
 > (<0.41.0>) call erlang:whereis(code_server)
 > (<0.41.0>) call erlang:make_ref()
 > (<0.41.0>) call erlang:node(code_server)
 > (<0.41.0>) call erlang:whereis(code_server)
 > (<0.41.0>) {'$gen_call',{<0.41.0>,#Ref},{ensure_loaded,gtk}} ! code_server
 > (<0.41.0>) << {#Ref,{module,gtk}}
 > (<0.41.0>) call erlang:function_exported(gtk,start_link,4)
 > (<0.41.0>) call erlang:element(1,{kernel,false})
 > (<0.41.0>) call erlang:element(1,{{default,all,font},{screen,12}})
 > (<0.41.0>) call erlang:spawn_link(gtk,init,[{1,<0.41.0>,<0.41.0>,[{kernel,false},{{default,all,font},{screen,12}}]}])
 > (<0.41.0>) spawn <0.42.0>
 > (<0.41.0>) link <0.42.0>
 > (<0.41.0>) << {'EXIT',<0.42.0>,
 >                       {choose_file,"/home/bhyde/work/erlang/erlang-47.4.0/erts-47.4.0/lib/gs-1.3.5/ebin/../priv/bin/",
 >                                    "wrap",
 >                                    [],
 >                                    {error,enoent}}}
 > ... then it just hangs.


And this is also expected since the buildlog (at your URL)
shows that the build failed just at the place where the above trace
tries to find the executable file
/home/bhyde .... /lib/gs-1.3.5/ebin/../priv/bin/wrap

So, here are your options.

1. Retry the gs build (read te README in gs/c_src very carefully)
2. Await the next release

/klacke

PS. I'm happy to see that you've found my good old trusty
'dbg' module, I thought I was the only user nowadays :-)