In message <52aa6f87d1chr...@care4free.net>
Chris Gransden wrote:
> In article ,
>Ron wrote:
>
> > I am sort of confused, I thought everything was to be built as e1f
> > now.
> > Is it just that EXT_EXE is mistakenly being set to ff8 somewhere?
>
> > I built libcurl3 successfully
In article ,
Ron wrote:
> I am sort of confused, I thought everything was to be built as e1f
> now.
> Is it just that EXT_EXE is mistakenly being set to ff8 somewhere?
> I built libcurl3 successfully but it accessed the unfinished bzip2
> directory source files to do it.
> It did look for Bzi
In message <20120703092216.gb...@chiark.greenend.org.uk>
Theo Markettos wrote:
> On Tue, Jul 03, 2012 at 06:29:38PM +1200, Ron wrote:
> > I have just tryed building the Nettle package a second time, to see
> > if it would put its packages in the correct place, but I get updates
> > then
In message
Ron wrote:
> In message <20120703092216.gb...@chiark.greenend.org.uk>
> Theo Markettos wrote:
>
>
> > Probably the autobuilder should handle this better, but I'm not sure how.
> > Perhaps detect that the tree is there and move it out of the way. Or be
> > ab
In message <20120703092216.gb...@chiark.greenend.org.uk>
Theo Markettos wrote:
> On Tue, Jul 03, 2012 at 06:29:38PM +1200, Ron wrote:
> > I have just tryed building the Nettle package a second time, to see
> > if it would put its packages in the correct place, but I get updates
> > then
On Tue, Jul 03, 2012 at 06:29:38PM +1200, Ron wrote:
> I have just tryed building the Nettle package a second time, to see
> if it would put its packages in the correct place, but I get updates
> then patch errors.
> I will try to attach the failure to this post
Hi Ron,
Are you running this on a
Ron wrote on Tuesday, July 03, 2012 7:29:
I've checked in the socketwatch autobuilder stuff now. If there
is someone who could build it and knows how to check its
OK, I will then rebuild it and upload it to the web.
I have done 'svn update' and ./build socketwatch without problems.
The two z
In message
"Alan Buckley" wrote:
> I've checked in the socketwatch autobuilder stuff now. If there
> is someone who could build it and knows how to check its
> OK, I will then rebuild it and upload it to the web.
>
> Regards,
> Alan
>
I have done 'svn update' and ./build socketwatch
Alex Macfarlane Smith wrote on June 14, 2012:
I notice that Frank's version is in objasm format, so theoretically
could be committed into Nettle's CVS
(http://nettle.cvs.sourceforge.net/viewvc/nettle/SocketWatch/ ), and
then someone could write an autobuilder for that.
Does that seem like a goo
On 14/06/2012 20:55, John Tytgat wrote:
In message <4fd9916f.2060...@archifishal.co.uk>
Alex Macfarlane Smith wrote:
On 12/06/2012 13:43, Frank de Bruijn wrote:> In article
,
> Alan Buckley wrote:
>> I notice it requires the SocketWatch module,
>
> You may want to look
In message <4fd9916f.2060...@archifishal.co.uk>
Alex Macfarlane Smith wrote:
> On 12/06/2012 13:43, Frank de Bruijn wrote:> In article
> ,
> > Alan Buckley wrote:
> >> I notice it requires the SocketWatch module,
> >
> > You may want to look at http://www.aconet.org/tools/sock
On 12/06/2012 13:43, Frank de Bruijn wrote:> In article
,
> Alan Buckley wrote:
>> I notice it requires the SocketWatch module,
>
> You may want to look at http://www.aconet.org/tools/socketwatch.zip
On 11/06/2012 13:21, Theo Markettos wrote:
SocketWatch's source is in BASIC, so it probabl
In article ,
Alan Buckley wrote:
> I notice it requires the SocketWatch module,
You may want to look at http://www.aconet.org/tools/socketwatch.zip
Years ago I fixed a memory leak in version 0.04y of that module -amongst
other things- and exchanged a couple of e-mails about it with one of the
In message <20120611122111.gh3...@chiark.greenend.org.uk>
Theo Markettos wrote:
> I have a CryptRandom package, but it currently relies on my
> private CVS repo. Would it be possible to host the repo on riscos.info?
> It's a fairly small project, so doing a cvs2svn on it and then impo
On 11/06/2012 15:11, Alan Buckley wrote:
Alex Macfarlane Smith wrote on Monday, June 11, 2012 2:29 PM:
On 11/06/2012 12:53, Alan Buckley wrote:
[snip]
> I notice it requires the SocketWatch module, if
> anyone could add that to the autobuilder as
> well we could upload it and add it as a
> de
Alex Macfarlane Smith wrote on Monday, June 11, 2012 2:29 PM:
On 11/06/2012 12:53, Alan Buckley wrote:
[snip]
> I notice it requires the SocketWatch module, if
> anyone could add that to the autobuilder as
> well we could upload it and add it as a
> dependcy to Nettle so we don't need to searc
On 11/06/2012 12:53, Alan Buckley wrote:
I wrote on Friday, June 08:
I've added the packaging steps to Nettle as well, so it
should now create a RiscPkg package.
If no one else does it, I'll try to get it built and uploaded
to the package site early next week.
I've now uploaded this to the
On Mon, Jun 11, 2012 at 12:53:08PM +0100, Alan Buckley wrote:
> I notice it requires the SocketWatch module, if
> anyone could add that to the autobuilder as
> well we could upload it and add it as a
> dependcy to Nettle so we don't need to search
> for it to get Nettle to work.
SSH mode also need
I wrote on Friday, June 08:
I've added the packaging steps to Nettle as well, so it
should now create a RiscPkg package.
If no one else does it, I'll try to get it built and uploaded
to the package site early next week.
I've now uploaded this to the packaging site. I built
it with GCC 4.1.2
Chris Gransden wrote on Thursday, June 07:
> In article ,
Alan Buckley wrote:
> I was going to look at the packaging, but can't get nettle to build
> on Cygwin or Debian. Do I need a particular version of the cross
> compiler?
> I seemed to get the same errors on both:
[snip errors]
In message
Ron wrote:
> In message <04046a7426d9971c8aef1dba551ebdff.squir...@www.archifishal.co.uk>
> "Alex Macfarlane Smith" wrote:
>
> > > In message
> > > <32b9f1a997c92f4b978d5a245ac0b232.squir...@www.archifishal.co.uk>
> > > compression dependancy stuff.
> > [snip]
>
On Thu, Jun 07, 2012 at 08:35:07AM +0100, Alan Buckley wrote:
> I seemed to get the same errors on both:
>
> sockwatch.o: In function `socketwatch_register':
> sockwatch.c:(.text+0x9c): undefined reference to `__get_ro_socket'
> sockwatch.o: In function `socketwatch_deregister':
> sockwatch.c:(.te
In message <04046a7426d9971c8aef1dba551ebdff.squir...@www.archifishal.co.uk>
"Alex Macfarlane Smith" wrote:
> > In message
> > <32b9f1a997c92f4b978d5a245ac0b232.squir...@www.archifishal.co.uk>
> > compression dependancy stuff.
> [snip]
> >
> > **I have emailed Theo, there is a "@rm !Ru
> In message
> <32b9f1a997c92f4b978d5a245ac0b232.squir...@www.archifishal.co.uk>
> compression dependancy stuff.
[snip]
>
> **I have emailed Theo, there is a "@rm !Runimage,elf" line in the
> GNUMakefile patch that needs to be removed so that you -do- get the
> !RunImage.
>
That should be fine, be
In message <32b9f1a997c92f4b978d5a245ac0b232.squir...@www.archifishal.co.uk>
compression dependancy stuff.
> >> I'm pretty sure libz is compiled, but I've no idea where
> >> __get_ro_socket comes from.
> >
> > I've checked in a fix for this, r5856. It just needed '-lz' adding to the
> > makefile.
> In article ,
>Alan Buckley wrote:
>
>> I was going to look at the packaging, but can't get nettle to build
>> on Cygwin or Debian. Do I need a particular version of the cross
>> compiler?
>
>> I seemed to get the same errors on both:
>
>> sockwatch.o: In function `socketwatch_register':
>> s
In article ,
Alan Buckley wrote:
> I was going to look at the packaging, but can't get nettle to build
> on Cygwin or Debian. Do I need a particular version of the cross
> compiler?
> I seemed to get the same errors on both:
> sockwatch.o: In function `socketwatch_register':
> sockwatch.c:(.
John Tytgat wrote on June 03, 2012:
In message <4fcb5a9d.1070...@archifishal.co.uk>
Alex Macfarlane Smith wrote:
> I've attached a patch for the nettle autobuilder, having firtled with
> the source upstream a bit :)
Thanks, I've commited your patch.
> I couldn't work out ho
In message <4fcb5a9d.1070...@archifishal.co.uk>
Alex Macfarlane Smith wrote:
> I've attached a patch for the nettle autobuilder, having firtled with
> the source upstream a bit :)
Thanks, I've commited your patch.
> I couldn't work out how to make it create a package (I just got rand
I've attached a patch for the nettle autobuilder, having firtled with
the source upstream a bit :)
I couldn't work out how to make it create a package (I just got random
errors about Nettle not being found and things), so I gave up :)
Alex.
Index: network/nettle/Run.p
30 matches
Mail list logo
