I'm working on some checks for this problem and will update the bootstrapper accordingly.
D. On Sun, Sep 7, 2008 at 2:29 AM, Martin Logan <[EMAIL PROTECTED]> wrote: > I am guessing that he is referencing the actual erts binary. Basically was > it compiled with the correct flags at the configure step.. > > On Sat, Sep 6, 2008 at 8:20 PM, Dave Smith <[EMAIL PROTECTED]> wrote: >> >> On Sat, Sep 6, 2008 at 7:07 PM, Eric Merritt <[EMAIL PROTECTED]> wrote: >> > >> > Is there anyway that we can verify that the binary was compiled the >> > correct way. Off the top of my head I guess we could parse the output >> > of erl (the flags at the top). I would love it if we could detect >> > erlang installs compiled incorrectly and not push them. >> >> Which binary in specific are you concerned about here? >> >> D. >> >> > >> > On Sat, Sep 6, 2008 at 10:18 AM, Martin Logan <[EMAIL PROTECTED]> >> > wrote: >> >> This is very nifty. I think we can put directions on the wiki and the >> >> google >> >> code page offering this as an alternate install method. This does not >> >> quite work yet though for me. Everything was installed into Erts 5.6.2 >> >> but >> >> faxien is compiled for 5.6.3 so when faxien went and tried to upgrade >> >> itself >> >> I got: >> >> >> >> Untaring into /usr/local/erlware >> >> >> >> *** Faxien is now installed *** >> >> >> >> Checking repos for any upgrades >> >> /usr/local/erlware/bin/faxien: line 25: >> >> /usr/local/erlware/packages/5.6.3/erts-5.6.3/bin/erlexec: No such file >> >> or >> >> directory >> >> >> >> >> >> On Sat, Sep 6, 2008 at 12:39 AM, Dave Smith <[EMAIL PROTECTED]> wrote: >> >>> >> >>> The sinan/faxien paradox for cutting new releases of the bootstrapper >> >>> has bugged me for some time. Today I finally sat down and did >> >>> something about it. I've just pushed up some new scripts in my private >> >>> faxien repo (git://github.com/dizzyd/faxien.git). These scripts enable >> >>> one to build a new bootstrapper for faxien using only the scripts and >> >>> a standard erlang install. >> >>> >> >>> So far, I've tested with Linux and OSX and everything seems to work >> >>> properly. I'd appreciate feedback if you guys can play with it a bit. >> >>> >> >>> Prerequisites: >> >>> * bash >> >>> * svn >> >>> * git >> >>> * Stock erlang somewhere (i.e. erlc is on your path) >> >>> >> >>> Getting started: >> >>> 1. Clone faxien from git://github.com/dizzyd/faxien.git >> >>> 2. cd scripts/bootstrapper >> >>> 3. ./bootstrap >> >>> >> >>> When it's all done, you'll have a new shell script that is the basic >> >>> faxien install. >> >>> >> >>> The only downside to this tool is that it assumes the HEAD of several >> >>> git repos is the released version (which is typically the case). >> >>> However, old bootstrappers (built by hand I suppose) had some version >> >>> discrepancies: >> >>> * cryptographic (on mainline erlware.git repo) is version 0.2.0 -- the >> >>> V6 bootstrapper includes a 0.2.1, so the repo must have unpushed >> >>> changes on someone's hard drive :) >> >> >> >> hmmm, I wonder who that could be :) >> >> >> >>> >> >>> * ewlib is version 0.8.2.0 (on mainline erlware.git repo) -- the V6 >> >>> bootstrapper includes 0.8.0.2 -- perhaps a typo? >> >> >> >> Nope, this is no typo, this is correct. The changes I made to fix the >> >> tar >> >> problem Matt highlighted minor revved the lib twice :-0 >> >> >> >> Cheers, >> >> Martin >> >>> >> >>> >> >>> >> >> >> >> >> >> > >> >> >> > >> > > >> > >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en -~----------~----~----~----~------~----~------~--~---
