I poked around the faxien source and found the faxien.hrl with all the
abbreviations and current commands.

Setting my preferred erts at 5.6.4 only upgraded hipe and 5.6.5 did
nothing.

-Tim

On Dec 6, 9:52 am, dysinger <[EMAIL PROTECTED]> wrote:
> Looks like this patch was already applied in git somewhere.  Rather
> than have me try to re-download 12b-3, scrape the patch off here and
> re-apply it - couldn't I pull from someone?  I see this is a git-patch
> below.
>
> Wouldn't it also work for one of you to push the mac vs of ssl-3.9 to
> the public repo for everyone?
>
> I don't even use 12b-3.  I was only using it inside erlware because
> it's the default and set-erts-version is broken.  I am on 12b-5
> outside of erlware.  What I wish is that I could just set my target at
> 12b-5, build and publish my own 12b-5 set of local apps and releases
> somehow.  I don't know the process well enough yet.
>
> On Dec 4, 8:47 pm, "Martin Logan" <[EMAIL PROTECTED]> wrote:
>
> > Thanks Mikael.
>
> > So this would mean that you need to compile r12b-3 on your machine,
> > the one with your target architecture and run 'faxien publish
> > <path-to-ssl-app>. Before building you would want to apply the the
> > patch that follows. Will that get you by.
>
> > From: Mikael Magnusson <[EMAIL PROTECTED]>
>
> > Signed-off-by: Mikael Magnusson <[EMAIL PROTECTED]>
> > ---
> >  lib/ewlib/src/ewl_file.erl |   14 ++++++++++++--
> >  1 files changed, 12 insertions(+), 2 deletions(-)
>
> > diff --git a/lib/ewlib/src/ewl_file.erl b/lib/ewlib/src/ewl_file.erl
> > index 503cc56..b328281 100644
> > --- a/lib/ewlib/src/ewl_file.erl
> > +++ b/lib/ewlib/src/ewl_file.erl
> > @@ -50,6 +50,7 @@
> >  %% Include Files
> >  %%--------------------------------------------------------------------
> >  -include("eunit.hrl").
> > +-include_lib("kernel/include/file.hrl").
>
> >  %%====================================================================
> >  %% External functions
> > @@ -88,8 +89,7 @@ delete_dir(Path) ->
> >  copy_dir(From, To) ->
> >     case filelib:is_dir(From) of
> >        false ->
> > -           {ok, _} = file:copy(From, To),
> > -           ok;
> > +           ok = copy_file(From, To);
> >        true ->
> >            case filelib:is_dir(To) of
> >                true  -> ok;
> > @@ -101,6 +101,16 @@ copy_dir(From, To) ->
> >     end.
>
> >  %%--------------------------------------------------------------------
> > +%% @doc copy a file including timestamps,ownership and mode etc.
> > +%% @spec copy_file(From::string(), To::string()) -> ok | {error, Reason}
> > +%% @end
> > +%%--------------------------------------------------------------------
> > +copy_file(From, To) ->
> > +    {ok, _} = file:copy(From, To),
> > +    {ok, FileInfo} = file:read_file_info(From),
> > +    file:write_file_info(To, FileInfo).
> > +
> > +%%--------------------------------------------------------------------
> >  %% @doc create a unique temorory directory.
> >  %% @spec create_tmp_dir(Prefix::string()) -> {ok, TmpDirPath} | {error, 
> > Reason}
> >  %% @end
> > --
> > 1.5.6.3
>
> > 2008/12/4 Mikael Magnusson <[EMAIL PROTECTED]>:
>
> > > On Thu, 2008-12-04 at 10:19 -0800, dysinger wrote:
> > >> Is there anyway there a working ssl app can be released in the
> > >> interim ?  I am still stuck.
>
> > > I have published ssl-3.9 for i686-pc-linux-gnu-glibc-2.3, but I guess
> > > you need it for one of the *-apple-* architectures?
>
> > > You could publish it yourself from OTP. I used erlang 12B-3 in Ubuntu
> > > Intrepid. But you need the following patch I sent to the list:
>
> > >    [erlware PATCH] copy file timestamps,ownership and mode together
> > > with the data
>
> > > /Mikael
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to