On Sat, Jul 30, 2011 at 7:10 PM, Tomek CEDRO wrote:
> Hello! :-) Trying to bootstrap on FreeBSD 8.2-RELEASE fails with the
> 0.5.0-rc2 as given at:
>
>
> http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=snapshot;h=d4cd6f032015552f00bf4b5a90f25f5f958e9d9e;sf=tgz
>
> This shoul
Hello! :-) Trying to bootstrap on FreeBSD 8.2-RELEASE fails with the
0.5.0-rc2 as given at:
http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=snapshot;h=d4cd6f032015552f00bf4b5a90f25f5f958e9d9e;sf=tgz
This should probably never happen with the "real" package as configure
scrip
On 14 July 2011 10:05, Luca Bruno wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jean-Christophe PLAGNIOL-VILLARD scrisse:
>
>
>> > But these are not really a real release, created by make dist.
>> > Surely we should be running make dist then uploading the releases to
>> > sourceforg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Christophe PLAGNIOL-VILLARD scrisse:
> > But these are not really a real release, created by make dist.
> > Surely we should be running make dist then uploading the releases to
> > sourceforge/berlios etc.
> >
> > Have you had a look at tools/r
On 13 July 2011 02:32, Andrew Leech wrote:
> On 11 July 2011 07:31, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
rc2
http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=snapshot;h=d4cd6f032015552f00bf4b5a90f25f5f958e9d9e;sf=tgz
> I'm assuming
On 13/07/2011, at 11:32 AM, Andrew Leech wrote:
> On 11 July 2011 07:31, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
rc2
http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=snapshot;h=d4cd6f032015552f00bf4b5a90f25f5f958e9d9e;sf=tgz
> I'm assumin
On 13/07/2011 11:48 AM, Peter Stuge wrote:
Andrew Leech wrote:
Again just a release tarball issue, but the tarball from above doesn't work
properly, it needs bootstrap run to get jimtcl etc
In particular for a release it's really really important that the two
separate packages (OpenOCD and jimt
Andrew Leech wrote:
> Again just a release tarball issue, but the tarball from above doesn't work
> properly, it needs bootstrap run to get jimtcl etc
In particular for a release it's really really important that the two
separate packages (OpenOCD and jimtcl) are *two separate packages*.
The tri
On 11 July 2011 07:31, Jean-Christophe PLAGNIOL-VILLARD
wrote:
rc2
http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=snapshot;h=d4cd6f032015552f00bf4b5a90f25f5f958e9d9e;sf=tgz
I'm assuming some testing would be good :-) I'm just moving into a
firmware project again, so
On 09:22 Mon 11 Jul , Spencer Oliver wrote:
> On 11 July 2011 07:31, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
> >> Totally agree on this - FreeBSD ports use automatic package download
> >> and extraction mechanism, so having tarball for RC2 would be great!
> >> Please let me know then its ava
Tarballs available for 0.4.0-rcs allowed me to build executables which
would show correct version on startup as well as PDF User's Guide with
correct tag. Now all people can see is "0.5.0-dev". "Real" release
tarballs would be really appreciated...
4\/3!!
__
On 11 July 2011 07:31, Jean-Christophe PLAGNIOL-VILLARD
wrote:
>> Totally agree on this - FreeBSD ports use automatic package download
>> and extraction mechanism, so having tarball for RC2 would be great!
>> Please let me know then its available :-)
> for RC we have us gitweb to generate the tar.
On Mon, Jul 11, 2011 at 6:31 AM, Jean-Christophe PLAGNIOL-VILLARD
wrote:
>> Totally agree on this - FreeBSD ports use automatic package download
>> and extraction mechanism, so having tarball for RC2 would be great!
>> Please let me know then its available :-)
> for RC we have us gitweb to generat
On 15:20 Sun 10 Jul , Tomek CEDRO wrote:
> On Sun, Jul 10, 2011 at 2:41 PM, Luca Bruno wrote:
> > As a sidenote, publishing tarball for -rc helps testing in conditions
> > similar to the final one, avoiding late bugs introduced by autotools
> > packaging or similar.
>
> Totally agree on this
On 16:59 Sun 10 Jul , Øyvind Harboe wrote:
> On the subject of tarballs for release candidates. I think David
> Brownell and Zach Welch used to do this.
>
> At least I think you presented some evidence that perhaps at least
> the *first* rc should be a tarball so as to catch any problems
w
On Sun, Jul 10, 2011 at 2:41 PM, Luca Bruno wrote:
> As a sidenote, publishing tarball for -rc helps testing in conditions
> similar to the final one, avoiding late bugs introduced by autotools
> packaging or similar.
Totally agree on this - FreeBSD ports use automatic package download
and extrac
On the subject of tarballs for release candidates. I think David
Brownell and Zach Welch used to do this.
At least I think you presented some evidence that perhaps at least
the *first* rc should be a tarball so as to catch any problems
--
Øyvind Harboe - Can Zylin Consulting help on your pro
Jean-Christophe PLAGNIOL-VILLARD scrisse:
> Here is OpenOCD v0.5.0-rc2
> This time on the official git tree
>
> The following changes since commit
> ff640f197a9a343b2f3ed10e9174e35282334e8c:
It looks like you forgot to push the corresponding tag.
I took the liberty to take this commi
Hi,
Today is RC day
Here is OpenOCD v0.5.0-rc2
This time on the official git tree
The following changes since commit ff640f197a9a343b2f3ed10e9174e35282334e8c:
cortex_m3: add auto maskisr (2011-06-28 14:16:48 +0100)
are available in the git repository at:
git://openo
19 matches
Mail list logo
