On 18-12-2015 09:31, David Kastrup wrote:
Villum Sejersen<v...@privat.tdcadsl.dk> writes:
If it did any difference to my system I would be glad, but that is
apparently /*not*/ the case!
root@Villums14:/usr/local/src/lilypond# ./autogen.sh --noconfigure
processing .
Running autoconf ...
Skipping configure process.
root@Villums14:/usr/local/src/lilypond# ./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking Package... LILYPOND
checking builddir... /usr/local/src/lilypond
checking for stepmake... ./stepmake (${datarootdir}/stepmake not found)
checking for gmake... no
checking for make... make
checking for find... find
checking for tar... tar
checking for bash... /bin/bash
checking for python... python
checking python version... 2.7.11
checking for python... /usr/bin/python
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/usr/local/src/lilypond':
configure: error: C compiler cannot create executables
See `config.log' for more details - (attached)
Uh, did you actually _bother_ reading the error message before posting
it? It definitely made a difference. You got further.
Oh, I always do bother, but apparently did not really understand what I
read. I am neither a programmer nor a musician, but a choir-singer, who
likes readable, beatiful scores better than bad copies of bad copies of
bad copies... ;)
I suggest
fixing the other problems in your build environment now:
configure:3874: checking whether the C compiler works
configure:3896: gcc conftest.c >&5
conftest.c:9:0: warning: "PACKAGE_NAME" redefined
#define PACKAGE_NAME "LilyPond"
^
conftest.c:2:0: note: this is the location of the previous definition
#define PACKAGE_NAME ""
^
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o: unrecognized
relocation (0x2a) in section `.init'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
configure:3900: $? = 1
configure:3938: result: no
You mangled your gcc installation to a degree where compiling and
linking a C binary without any options has become impossible.
No! /debian stretch testing/ did it /without any alterations
whatsoever/ from my side... ;)
Updates to gcc and all derived application was done in two portions, one
two days ago and one this morning... There must have been a README.txt
to the first installment, the significance of which I apparently did not
understand. ;(
After the second update the relocation(s) were automatically found as
usual. What really happened inbetween I wonder.
Nope. What parts of stepmake LilyPond needs are included in LilyPond
itself.
Well, that's good to know, but where is it documented?
Documenting all non-dependencies would be excessive.
Then I suggest that at least 1.9 in INSTALL.txt should be reformulated.
As written now it is really confusing, leading - as I did - to expect to
have to look for an external dependency.
Once more:
Thank you for your patience.
Both lilypond-devel and lilypond-doc are now compiled and installed.
BTW.: The docs take about two hours on my ancient AMD Athlon X2, but to
me it's worthwhile to have the newest docs to look up in Frescobald.
--
yours,
Villum Sejersen
Nørregade 1 A
DK-4500 Nykøbing Sjælland
mobil +45 30 34 03 44
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
