I have just pushed a possible fix as http://openocd.zylin.com/5545
Would be good to have feedback from Ake and also if there is any other
issue in his build environment.
I'm trying to figure out if we can test this case without newlib ...
Antonio
On Thu, Mar 26, 2020 at 10:31 PM John S via OpenOC
I think it means array ELEMENT, not subscript, has type char.
(Also, once upon a time char widened to int...)
John
On Thursday, 26 March 2020, 21:23:41 GMT, Åke Rehnman
wrote:
Hello all,
newlib forces parameter c to isalnum(c) to be unsigned char or int.
BR
/Ake
In file included
Hello all,
newlib forces parameter c to isalnum(c) to be unsigned char or int.
BR
/Ake
In file included from ../src/helper/system.h:29,
from ./config.h:338,
from ../src/flash/nor/nrf5.c:22:
../src/flash/nor/nrf5.c: In function ‘nrf5_info_variant_to_str’:
../sr
Hi,
On Sat, Sep 06, 2014 at 10:55:20AM +0200, Hector Garcia de Marina wrote:
> today I have updated my copy of the openocd repository (since almost one year
> I
> have not updated it) and I have the next compilation error regarding
> hla_transport (pasted at the end of this mail).
I think that's
On Sat, Sep 6, 2014 at 11:12 AM, Hector Garcia de Marina
wrote:
> Sorry for the spam, it was my fault
>
> just I have run ./bootstrap again and everything is compiling fine now.
>
No problem.
It was git submodule update (part of bootstrap) that did the trick. JimTcl
had an API change so the Jim
Sorry for the spam, it was my fault
just I have run ./bootstrap again and everything is compiling fine now.
On Sat, Sep 6, 2014 at 10:55 AM, Hector Garcia de Marina
wrote:
> Hi,
>
> today I have updated my copy of the openocd repository (since almost one
> year I have not updated it) and I have
Hi,
today I have updated my copy of the openocd repository (since almost one
year I have not updated it) and I have the next compilation error regarding
hla_transport (pasted at the end of this mail).
My OS is Debian Stable (Wheezy) 64bits. I do not know if it is "wise" to
ignore this warning err
On Mon, Oct 7, 2013 at 11:39 PM, Freddie Chopin wrote:
> I've taken a look at the script and it all seems nice, but I guess the
> problem would be with libusb-win32, which I cannot build "completely" -
> it fails after the DLLs and static libs are built, and I don't need
> anything more, so I wasn
I've taken a look at the script and it all seems nice, but I guess the
problem would be with libusb-win32, which I cannot build "completely" -
it fails after the DLLs and static libs are built, and I don't need
anything more, so I wasn't fixing that...
4\/3!!
--
Hi Freddie,
Freddie Chopin wrote:
> Any luck with that? I was planinig to do another snapshot compilation
> soon, but I guess it will be pretty hard this time...
>
> If I have the libs in right places, can I just provide some flags
> externally to avoid all the hassle? sth like LDFLAGS="..." c
Nader wrote:
> please if you were able to compile
..
> beta releases can be helpful in eliminating unnecessary issues.
You should build it yourself so that you can help eliminate
unneccessary issues.
//Peter
--
October
Hi Freddie and all,
Thanks for the previous releases for Windows, please if you were able
to compile any snapshot for windows, to test , that would be appreciated.
We understand it is not the official committed release, but beta releases
can be helpful in eliminating unnecessary issues.
Cheer
W dniu 2013-10-04 15:25, Jonathan Dumaresq pisze:
> Hi,
>
>>
>> git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd
>> openocd-git
>> cd openocd-git
>> ./bootstrap
>>
>>
>> + aclocal
>> + libtoolize --automake --copy
>> + autoconf
>> configure.ac:228: error: possibly undefined macro
On Fri, Oct 4, 2013 at 3:25 PM, Jonathan Dumaresq wrote:
>
> I got some probleme now with the detection of the libusb1.x I will try to
> find what change in that too.
>
Hi!
See contrib/cross-build.sh for an example of how to properly cross-compile
OpenOCD.
/Andreas
-
Hi,
>
> git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd
> openocd-git
> cd openocd-git
> ./bootstrap
>
>
> + aclocal
> + libtoolize --automake --copy
> + autoconf
> configure.ac:228: error: possibly undefined macro: AC_MSG_NOTICE
> If this token and others are legitima
Hi,
I try to recompile the latest version of openocd and I have some probleme
with autoconf.
I'm cross compile from ubuntu to windows
Here the version
dumarjo@OpenOCD:~$ autoconf --version
autoconf (GNU Autoconf) 2.68
git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd
openocd
On 03/07/2012 20:23, st...@nixia.no wrote:
>> I have already do the Makefile.am part, and it's create a good (I think,
>> I hope) Makefile
>> :(
>> I don't understand because if I change my ./configure option line from
>> ./configure --with-ft2232-lib=static --disable-werror (The one I use) to
>> .
On 03/07/2012 22:18, Peter Stuge wrote:
> Vivien Giraud wrote:
>> I need it to be have libftdi and libusb static
> Just a side note: Keep in mind that libusb is licensed under LGPL,
> and OpenOCD under GPL, so you can not legally distribute only a
> statically linked binary.
>
> I assume that you a
Vivien Giraud wrote:
> I need it to be have libftdi and libusb static
Just a side note: Keep in mind that libusb is licensed under LGPL,
and OpenOCD under GPL, so you can not legally distribute only a
statically linked binary.
I assume that you are working on making a custom tool for a
custom deb
> I have already do the Makefile.am part, and it's create a good (I think,
> I hope) Makefile
> :(
> I don't understand because if I change my ./configure option line from
> ./configure --with-ft2232-lib=static --disable-werror (The one I use) to
> ./configure --enable-ft2232-lib --disable-werror (
On 03/07/2012 18:12, st...@nixia.no wrote:
>> I have add this in makefile :
>>
>> libopenocd_la-detection.lo: detection.c
>> $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS)
>> --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES)
>> $(libopenocd_la_CPPFLAGS)
> I have add this in makefile :
>
> libopenocd_la-detection.lo: detection.c
> $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS)
> --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES)
> $(libopenocd_la_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT
>...
You shou
> Here is my error
>
> /bin/bash ../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2
> -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra
> -Wno-unused-parameter -Wbad-function-cast -Wcast-align
> -Wredundant-decls -o openocd main.o libopenocd.la
> ../jimtcl/lib
On 03/07/2012 17:22, st...@nixia.no wrote:
Here is my error
/bin/bash ../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2
-Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra
-Wno-unused-parameter -Wbad-function-cast -Wcast-align
-Wredundant-decls -o openocd ma
Hi,
I'm adding new functions to some files and I have a problem when I
compiling it, may I have to change something in makefile or other.
Here is my error
/bin/bash ../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2
-Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra
-Wn
25 matches
Mail list logo
