openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kay Schenk <kay.sch...@gmail.com>
Subject unexpected behavior from configure -- new env script not generated
Date Tue, 13 Aug 2013 19:03:58 GMT
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
while to track this down and just delete my existing shell environment
script. Then the configure worked as expected. This was the ONLY change in
my configure params

Any guesses as to the cause of this?
* Is this a problem with *my* system autoconf or configure ?
* is this how things normally work and we should document this in the build
instructions ?

I'm looking at configure.in etc but since I'm not an autoconf guru, well,
what to do.

-- 
-------------------------------------------------------------------------------------------------
MzK

Success is falling nine times and getting up ten."
                             -- Jon Bon Jovi

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message