search

vslavik / bakefile

Bakefile makefiles generator
http://bakefile.org
MIT License
142 stars 20 forks source link

legacy-0.2-branch: problem with man pages #120

Open ardovm opened 4 years ago

ardovm commented 4 years ago

The current legacy-0.2-branch does not build man pages (i.e. files in doc/man) unless the parameter --enable-maintainer-mode is passed to the configure script. But the Makefile that is generated for the doc directory depends on those files:

MANPAGES = man/bakefile.1 man/bakefilize.1 man/bakefile_gen.1

This stops make right before the compilation of the sources:

$ ./configure
 [ ... ]
$ make
Making all in doc
make[1]: Entering directory '/home/user/bakefile/doc'
make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'.  Stop.
make[1]: Leaving directory '/home/user/bakefile/doc'
Makefile:1023: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
vslavik commented 4 years ago

Generated manpages are part of the tarball; it is intentional than they aren't rebuilt.

If you're building from the repository, you need to follow the README's instructions for that and run the ./bootstrap script.

ardovm commented 4 years ago

Thank you for your fast reply. That is what I did. Following the README, I installed all the required software:

On a newly fetched working copy of the branch:

$ ./bootstrap                                      
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.
in'                                                                             
automake: warning: autoconf input should be named 'configure.ac', not 'configure
.in'                                                                            
configure.in:14: installing 'admin/compile'                                     
configure.in:8: installing 'admin/config.guess'                                 
configure.in:8: installing 'admin/config.sub'                                   
configure.in:11: installing 'admin/install-sh'                                  
configure.in:11: installing 'admin/missing'                                     
automake: warning: autoconf input should be named 'configure.ac', not 'configure
.in'                                                                            
Makefile.am:130: warning: source file 'src/bottlenecks.c' is in a subdirectory, 
Makefile.am:130: but option 'subdir-objects' is disabled                        
automake: warning: possible forward-incompatibility.                            
automake: At least a source file is in a subdirectory, but the 'subdir-objects' 
automake: automake option hasn't been enabled.  For now, the corresponding outpu
t                                                                               
automake: object file(s) will be placed in the top-level directory.  However,   
automake: this behaviour will change in future Automake versions: they will     
automake: unconditionally cause object files to be placed in the same subdirecto
ry                                                                              
automake: of the corresponding sources.                                         
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.                         
Makefile.am:130: warning: source file 'src/bkl_c_wrap.c' is in a subdirectory,
Makefile.am:130: but option 'subdir-objects' is disabled
Makefile.am: installing 'admin/depcomp'
Makefile.am:101: installing 'admin/py-compile'
$ > ./configure && make && make install
[...configure output...]
Making all in doc
make[1]: Entering directory '/home/user/bakefile/doc'
make[1]: *** No rule to make target 'man/bakefile.1', needed by 'all-am'.  Stop.
make[1]: Leaving directory '/home/user/bakefile/doc'
make: *** [Makefile:1022: all-recursive] Error 1
ardovm commented 4 years ago

I thought there was a better way to attach files, but I could not find it. Here is the output of the configure script:

configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
checking build system type... x86_64-pc-linux-gnu                               
checking host system type... x86_64-pc-linux-gnu                                
checking for a BSD-compatible install... /usr/bin/install -c         
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk                                                       
checking whether make sets $(MAKE)... yes                                       
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc                                                         
checking whether the C compiler works... yes                                    
checking for C compiler default output file name... a.out                       
checking for suffix of executables...                                           
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld
checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop 
checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for a Python interpreter with version >= 2.3.0... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... ${exec_prefix}/lib64/python2.7/site-packages
checking for Python include path... /usr/include/python2.7
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
vslavik commented 4 years ago

Sorry, I was certain the bootstrap script runs docbook. Patches welcome then, I guess; when submitted, I apply them to the legacy branch too despite its legacy status.

vslavik commented 2 years ago

@barracuda156 please avoid mention-spamming. The very issue you're commenting on tells you what to do: use maintainer mode.

barracuda156 commented 2 years ago

@vslavik Thank you again, that worked. Silly me.

There is another issue you may want to fix with configure, on newer MacOS python in usr/bin is not detected correctly:

checking whether /usr/bin/python version is >= 2.3.0... no
  configure: error: Python interpreter is too old
  Command failed:  cd "/opt/local/var/macports/build/_Users_runner_work_macports-ports_macports-ports_ports_devel_bakefile/bakefile/work/bakefile-0.2.13" && ./configure --prefix=/opt/local --enable-maintainer-mode 
  Exit code: 1

https://github.com/macports/macports-ports/actions/runs/3214670730/jobs/5255218833

This is not a big deal for Macports, since we can make it depend on python27 port across all systems, but perhaps still worth fixing.

Apteryks commented 1 year ago

OK, I had missed it in the above thread somehow; the manpages are only built when the build system is configured in "maintainer mode", like so:

./configure --enable-maintainer-mode