Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-20 Thread Paul Fertser
Hey Liviu, Andreas, I believe there's some misunderstanding happening. We all know both of you do a big job at providing free software community with great software. So it's just a matter of priorities. You file a feature request asking for configure to guard against some user errors (as enabling

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-20 Thread Liviu Ionescu
> On 20 Nov 2016, at 12:16, Andreas Fritiofson > wrote: > > If you benefit from the change, why don't you do the work yourself? what benefit do you think I have from maintaining GNU ARM Eclipse OpenOCD? none. I personally do not use OpenOCD at all, and I cannot recommend it to my clients. ho

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-20 Thread Andreas Fritiofson
On Sat, Nov 19, 2016 at 11:42 PM, Liviu Ionescu wrote: > > > On 20 Nov 2016, at 00:13, Andreas Fritiofson < > andreas.fritiof...@gmail.com> wrote: > > > > Supposedly packagers should be familiar with the options and the > platform capabilities. > > it's a meter of courtesy to your colleagues, if

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-19 Thread Xiaofan Chen
On Sun, Nov 20, 2016 at 6:13 AM, Andreas Fritiofson wrote: > > On Sat, Nov 19, 2016 at 2:59 AM, Xiaofan Chen wrote: >> Probably it is just easier to detect Mac OS X >> and automatically disable Parallel Port based adapters. > > > Well, I'm just interested in whether my autotools changes has cause

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-19 Thread Liviu Ionescu
> On 20 Nov 2016, at 00:13, Andreas Fritiofson > wrote: > > Supposedly packagers should be familiar with the options and the platform > capabilities. it's a meter of courtesy to your colleagues, if you know that certain combinations of options do not make sense, it would take you significan

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-19 Thread Andreas Fritiofson
On Sat, Nov 19, 2016 at 2:59 AM, Xiaofan Chen wrote: > On Sat, Nov 19, 2016 at 7:18 AM, Andreas Fritiofson > wrote: > > On Fri, Nov 18, 2016 at 11:31 PM, Liviu Ionescu wrote: > >> with --disable-amtjtagaccel & --disable-gw16012, the macOS build passed. > >> > > Do these two build on master? I g

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-19 Thread Liviu Ionescu
> On 19 Nov 2016, at 03:59, Xiaofan Chen wrote: > > I doubt Mac OS X ever supported bitbang on Parallel Port. that's correct, I doubt recent Macs ever had a Parallel Port, at least since 2009 I haven't seen one. but it might be possible to connect a Parallel Port via USB, as it is done for Se

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-19 Thread Liviu Ionescu
> On 19 Nov 2016, at 03:59, Xiaofan Chen wrote: > > detect Mac OS X > and automatically disable Parallel Port based adapters. even more, configure should issue an error if the user tries to enable them. regards, Liviu

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-18 Thread Xiaofan Chen
On Sat, Nov 19, 2016 at 7:18 AM, Andreas Fritiofson wrote: > On Fri, Nov 18, 2016 at 11:31 PM, Liviu Ionescu wrote: >> with --disable-amtjtagaccel & --disable-gw16012, the macOS build passed. >> > Do these two build on master? I guess not. > > Why do you disable parport? That one also uses the sa

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-18 Thread Andreas Fritiofson
On Fri, Nov 18, 2016 at 11:31 PM, Liviu Ionescu wrote: > > > with --disable-amtjtagaccel & --disable-gw16012, the macOS build passed. > > Do these two build on master? I guess not. Why do you disable parport? That one also uses the same condition to include sys/io.h so it would probably also fai

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-18 Thread Liviu Ionescu
> On 19 Nov 2016, at 00:00, Liviu Ionescu wrote: > > for the moment I'll disable these options from all my builds. gw16012.c too: /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/Users/ilg/Work/openocd/gnuarmeclipse-openocd.git/src/jtag/drivers -I../../.. -I/

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-18 Thread Liviu Ionescu
> On 19 Nov 2016, at 00:00, Liviu Ionescu wrote: > > for the moment I'll disable these options from all my builds. with the new configuration the macOS build fails while compiling amt_jtagaccel.c: /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/Users/ilg/Work

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-18 Thread Liviu Ionescu
> On 18 Nov 2016, at 22:51, Andreas Fritiofson > wrote: > > > > On Fri, Nov 18, 2016 at 3:33 PM, Liviu Ionescu wrote: > while preparing GNU ARM Eclipse OpenOCD for the announced 0.10.0 release, I > tried to enable the new configure options, and I encountered the following > problems: > >

Re: [OpenOCD-devel] 0.10.0 build errors

2016-11-18 Thread Andreas Fritiofson
On Fri, Nov 18, 2016 at 3:33 PM, Liviu Ionescu wrote: > while preparing GNU ARM Eclipse OpenOCD for the announced 0.10.0 release, > I tried to enable the new configure options, and I encountered the > following problems: > > on macOS 10.12: > > - --enable-oocd_trace fails with undeclared identifi

[OpenOCD-devel] 0.10.0 build errors

2016-11-18 Thread Liviu Ionescu
while preparing GNU ARM Eclipse OpenOCD for the announced 0.10.0 release, I tried to enable the new configure options, and I encountered the following problems: on macOS 10.12: - --enable-oocd_trace fails with undeclared identifier 'B250' (https://sourceforge.net/p/openocd/tickets/137/) o