Re: [Erlangweb-users] Operator error or perhaps a bug report
Brought to you by:
etcerlangweb,
paulgray
|
From: Michal P. <pau...@gm...> - 2008-11-07 08:34:51
|
Hello! 2008/11/7 Paul R. Bernard <pr...@do...>: > I've been playing with erlangweb-1.1 and I had a bit of trouble > getting it started. I'm using Erlang R12B-4 on a stable up to date > Gentoo system. I'm using the supplied yaws 1.73 rather than my own. > > I've read the tutorial. It's not clear to me if the initial > bin/start.erl escript is *supposed* to be run in an empty directory of > my choosing or whether it can only be run where I chose to unpack and > make the erlang-web distribution. Thanks for that remark - we will correct the tutorial so everything will be cleaner. > I may be having erlang environment troubles or I might be having PEBKAC > troubles. If I run the escript inside the erlangweb distribution > directory everything works just fine. (Well almost just fine, there are > some non-portable nits in the various scripts (and the already known > en.conf problem) but once fixed it goes ok.) > > If I run the escript inside an empty directory *with* ERL_LIBS set to an > appropriate ".../erlangweb-1.1/lib" value it seems to be fine. (with > the exception that there's a mixup between the yaws.conf file and > yaws.config pre-configured in the skeleton). Once the problems are > fixed it still won't go. Here's why. > > The following files and directories are NOT copied by the escript > > yaws-1.73/include/* > > lib/wpart-1.1/ebin/utf8.beam > lib/wpart-1.1/ebin/utf8_api.beam > lib/wpart-1.1/ebin/validate_tool.beam > lib/wpart-1.1/ebin/wpart_utils.beam > > and > > lib/wparts-1.1/ebin/wpart_gen.beam > > Once these are copies it works great. > > I don't have any experience (beyond this one) working with erlang > releases or huge or elaborate erlang setups. I've not looked further > into trying to figure out why these particular beam files are not > copied, every other beam file is copied. I have checked the .app files and noticed, that we have missed those files in modules section. So once again - thank you for pointing out that bug :) Best regards, Michal Ptaszek > > - paul |