Issue 6877 - Error in the autogen.sh file from dmake
Summary: Error in the autogen.sh file from dmake
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: current
Hardware: Other Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: foskey
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-09 10:33 UTC by svenl
Modified: 2003-03-17 00:20 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description svenl 2002-08-09 10:33:15 UTC
Hi! 
 
If you whant to compile dmake it says: 
 
You must have autoconf version 2.13 installed to compile dmake. 
Get ftp://ftp.gnu.org/gnu/gettext/autoconf/autoconf-2.13.tar.gz 
 
If you have a newer version, too. 
Can somebody fix this build bug! 
 
Sven
Comment 1 foskey 2002-08-09 13:00:39 UTC
Can you post the actual messages  I cannot see anything obvious.

Try the following and let us know the results.

ln -s configure.in configure.ac
Comment 2 svenl 2002-08-09 13:30:10 UTC
Hi! 
 
This was the output from "bootstrap". It looks like he can make it. 
But at the end he generate no makefiles and so he break with an 
error. The Test was in the "autogen.sh" file. There was a grep on 
that special version and if you have a higher version it faild, too. 
I have installed the Version 2.52 from autoconf. 
 
==================================================================== 
 
sven kde3/staroffice# ./bootstrap 
 
You must have autoconf version 2.13 installed to compile dmake. 
Get ftp://ftp.gnu.org/gnu/gettext/autoconf/autoconf-2.13.tar.gz 
creating cache ./config.cache 
checking for a BSD compatible install... /usr/bin/ginstall -c 
checking whether build environment is sane... yes 
checking whether make sets ${MAKE}... yes 
checking for working aclocal... found 
checking for working autoconf... found 
checking for working automake... found 
checking for working autoheader... found 
checking for working makeinfo... found 
checking for c++... c++ 
checking whether the C++ compiler (c++  ) works... yes 
checking whether the C++ compiler (c++  ) is a cross-compiler... no 
checking whether we are using GNU C++... yes 
checking whether c++ accepts -g... yes 
checking for gcc... gcc 
checking whether the C compiler (gcc  ) works... yes 
checking whether the C compiler (gcc  ) is a cross-compiler... no 
checking whether we are using GNU C... yes 
checking whether gcc accepts -g... yes 
checking how to run the C preprocessor... gcc -E 
checking for a BSD compatible install... /usr/bin/ginstall -c 
checking whether ln -s works... yes 
checking whether make sets ${MAKE}... (cached) yes 
checking for ranlib... ranlib 
checking for dirent.h that defines DIR... yes 
checking for opendir in -ldir... no 
checking for ANSI C header files... yes 
 
==================================================================== 
Comment 3 Unknown 2002-10-09 13:10:01 UTC
I assume this issue is fixed as bootstrap no longer calls 
autoconf (see changes in config_office/bootstrap.1 file)
Comment 4 foskey 2002-10-09 13:34:45 UTC
This is still an issue for the configure script.  Will remove,  update
requirement for a windows build to use bootstrap as well.

The current process magically creates dmake in the .Set file.
Comment 5 chris 2003-02-13 08:43:02 UTC
Ken, is this done yet?  Reassigning to you :)
Comment 6 foskey 2003-02-13 10:45:42 UTC
This is now closed,  we do not use the autogen shell script.
Comment 7 foskey 2003-03-17 00:08:06 UTC
This is not currently a problem on any working branch.
Comment 8 foskey 2003-03-17 00:20:10 UTC
Closing issue.