On Wed, Feb 17, 2010 at 4:47 PM, David Brownell wrote:
>> Maybe it is not a real bug after all since there is a work-around to
>> specify CFLAGS and LDFLAGS to get it built.
>
> That's how it's installed on one of my machines. "configure" needs to
> be fed those flags ... otherwise "openocd" won'
On Wed, Feb 17, 2010 at 4:47 PM, David Brownell wrote:
>> Maybe it is not a real bug after all since there is a work-around to
>> specify CFLAGS and LDFLAGS to get it built.
>
> That's how it's installed on one of my machines. "configure" needs to
> be fed those flags ... otherwise "openocd" won'
On Wednesday 17 February 2010, Xiaofan Chen wrote:
> > So I just tested it under Linux, if I install libftdi to /usr/local (which
> > is the default if you build from source), it will fail to build.
> >
> > I will tend to think this is a bug.
> >
>
> Maybe it is not a real bug after all since ther
On Wed, Feb 17, 2010 at 4:00 PM, Xiaofan Chen wrote:
>> Actually I consider this a bug of OpenOCD. /usr/local should
>> be searched, even under Linux.
>>
>
> So I just tested it under Linux, if I install libftdi to /usr/local (which
> is the default if you build from source), it will fail to build
On Mon, Feb 15, 2010 at 9:47 AM, Xiaofan Chen wrote:
> On Mon, Feb 15, 2010 at 9:36 AM, CeDeROM wrote:
>> Ah yes, OpenOCD's configure script can also assume using
>> "/usr/local/lib" and "/usr/local/include" to search for libraries and
>> header files - it would be nice, however if it don't the P
