Re: compilation fails with gnu make
Am 12.12.2015 um 22:14 schrieb Richard Heck :
> On 12/12/2015 03:46 PM, Jean-Marc Lasgouttes wrote:
>> Le 12/12/15 21:37, Guenter Milde a écrit :
>>> Most times it is not necessary to run configure. Just "make" suffices.
>>> How can I tell when autogen and configure are required? Or is it good
>>> practice to try them whenever compilation fails?
>>
>> It should not be needed, but sometimes it is and I do not know why. So
>> indeed it is a good thing to try that when makefiles cause problems.
>
> If one of the Makefile.am files changes, then it is needed to regenerate
> Makefile.in, which configure then uses. Right?
This is part of my build script in development/LyX-Mac-binary-release.sh:
# -
# Automate configure check
# -
if [ ! -f "${LyxSourceDir}"/configure -o "${LyxSourceDir}"/configure -ot
"${LyxSourceDir}"/configure.ac ]; then
( cd "${LyxSourceDir}" && sh autogen.sh )
else
find "${LyxSourceDir}" -name Makefile.am -print | while read file ; do
dname=$(dirname "$file")
if [ -f "$dname/Makefile.in" -a "$dname/Makefile.in" -ot "$file" ]; then
( cd "${LyxSourceDir}" && sh autogen.sh )
break
fi
done
fi
… and it works reliable for me.
The code checks for missing or outdated configure first and then looks for
occurrences of directories with Makefile.am and missing or outdated Makefile.in.
Stephan
Re: compilation fails with gnu make
Richard Heck wrote: > On 12/12/2015 03:46 PM, Jean-Marc Lasgouttes wrote: >> Le 12/12/15 21:37, Guenter Milde a écrit : >>> Most times it is not necessary to run configure. Just "make" suffices. >>> How can I tell when autogen and configure are required? Or is it good >>> practice to try them whenever compilation fails? >> >> It should not be needed, but sometimes it is and I do not know why. So >> indeed it is a good thing to try that when makefiles cause problems. > > If one of the Makefile.am files changes, then it is needed to regenerate > Makefile.in, which configure then uses. Right? Yes. Most of the time this is done automatically, there are rules in Makefile to regenerate Makefile.in and to rerun configure. In some cases this does not work (if too much changed in Makefile.am), and it usually is not obvious that the problem would be solved by simply rerunning autogen.sh and configure. Therefore I always run autogen.sh and configure before compiling with autotools, and these errors do not happen. Georg
Re: compilation fails with gnu make
On 12/12/2015 03:46 PM, Jean-Marc Lasgouttes wrote: > Le 12/12/15 21:37, Guenter Milde a écrit : >> Most times it is not necessary to run configure. Just "make" suffices. >> How can I tell when autogen and configure are required? Or is it good >> practice to try them whenever compilation fails? > > It should not be needed, but sometimes it is and I do not know why. So > indeed it is a good thing to try that when makefiles cause problems. If one of the Makefile.am files changes, then it is needed to regenerate Makefile.in, which configure then uses. Right? Richard
Re: compilation fails with gnu make
Le 12/12/15 21:37, Guenter Milde a écrit : Most times it is not necessary to run configure. Just "make" suffices. How can I tell when autogen and configure are required? Or is it good practice to try them whenever compilation fails? It should not be needed, but sometimes it is and I do not know why. So indeed it is a good thing to try that when makefiles cause problems. JMarc
Re: compilation fails with gnu make
On 2015-12-10, Stephan Witt wrote: > Am 10.12.2015 um 10:17 schrieb Guenter Milde : >> compilation via `make` after a >> ../lyx/configure --enable-build-type=release --with-version-suffix=-svn >> failed with error >> make[3]: Entering directory '/usr/local/src/lyxbuild/lib' >> GEN lyx-svn.desktop >> make[3]: *** No rule to make target 'images/all-changes-accept.png', needed >> by 'all-am'. Schluss. >> It seems there is some cleanup required after >> db363ab19f6051bb7b7af3fc88/lyxgit "Remove unneeded png images." > Did you run autogen.sh before configure? Yes, some weeks or months ago. Most times it is not necessary to run configure. Just "make" suffices. How can I tell when autogen and configure are required? Or is it good practice to try them whenever compilation fails? Günter
Re: compilation fails with gnu make
Am 10.12.2015 um 10:17 schrieb Guenter Milde : > Dear LyXers, > > compilation via `make` after a > ../lyx/configure --enable-build-type=release --with-version-suffix=-svn > failed with error > > make[3]: Entering directory '/usr/local/src/lyxbuild/lib' > GEN lyx-svn.desktop > make[3]: *** No rule to make target 'images/all-changes-accept.png', needed > by 'all-am'. Schluss. > > > It seems there is some cleanup required after > db363ab19f6051bb7b7af3fc88/lyxgit "Remove unneeded png images." Did you run autogen.sh before configure? Stephan
compilation fails with gnu make
Dear LyXers, compilation via `make` after a ../lyx/configure --enable-build-type=release --with-version-suffix=-svn failed with error make[3]: Entering directory '/usr/local/src/lyxbuild/lib' GEN lyx-svn.desktop make[3]: *** No rule to make target 'images/all-changes-accept.png', needed by 'all-am'. Schluss. It seems there is some cleanup required after db363ab19f6051bb7b7af3fc88/lyxgit "Remove unneeded png images." Günter
