On Wed, Aug 14, 2013 at 5:28 AM, Andre Fischer wrote:
> On 13.08.2013 23:02, Kay Schenk wrote:
>
>> On Tue, Aug 13, 2013 at 12:16 PM, janI wrote:
>>
>> On 13 August 2013 21:03, Kay Schenk wrote:
>>>
>>> Yesterday, I did a dmake clean to start over with my build, and then
proceded with au
Hi,
On 14.08.2013 14:28, Andre Fischer wrote:
On 13.08.2013 23:02, Kay Schenk wrote:
On Tue, Aug 13, 2013 at 12:16 PM, janI wrote:
On 13 August 2013 21:03, Kay Schenk wrote:
Yesterday, I did a dmake clean to start over with my build, and then
proceded with autoconf and configure. I had ch
On 13.08.2013 23:02, Kay Schenk wrote:
On Tue, Aug 13, 2013 at 12:16 PM, janI wrote:
On 13 August 2013 21:03, Kay Schenk wrote:
Yesterday, I did a dmake clean to start over with my build, and then
proceded with autoconf and configure. I had chagned my ant version a
while
back and this was
On Tue, Aug 13, 2013 at 12:16 PM, janI wrote:
> On 13 August 2013 21:03, Kay Schenk wrote:
>
> > Yesterday, I did a dmake clean to start over with my build, and then
> > proceded with autoconf and configure. I had chagned my ant version a
> while
> > back and this was reflected in my configure c
On 13 August 2013 21:03, Kay Schenk wrote:
> Yesterday, I did a dmake clean to start over with my build, and then
> proceded with autoconf and configure. I had chagned my ant version a while
> back and this was reflected in my configure call. Much to my surprise, the
> old ant version seemed to b
Yesterday, I did a dmake clean to start over with my build, and then
proceded with autoconf and configure. I had chagned my ant version a while
back and this was reflected in my configure call. Much to my surprise, the
old ant version seemed to be "stuck' in configure's brain, and it took me a
whil
