Malte, Did you ever manage to figure this out?
Over the last couple of days I have had to reinstall my dev env on Linux and have also been seeing how convenient it is to move to a later version of my current distribution, and have not had the same error as you have here when having to install from scratch. This leads me to believe that this is something, possibly, environmental to your own machine than generic. I have been using Ubuntu though. James -----Original Message----- From: lilypond-devel <[email protected]> On Behalf Of Malte Meyn Sent: 08 January 2019 10:01 To: [email protected] Subject: Re: linker error: DSO missing from command line Am 08.01.19 um 10:47 schrieb James Lowe: > Hello Malte > > On 08/01/2019 8:22 am, Malte Meyn wrote: >> Hi list, >> >> in a clean repository (in a branch based on current origin/master) I >> did the following: >> >> $ ./autogen.sh > > not ./autogen.sh --noconfigure? (I don't know what this does but it is > what I do for out of tree builds) Uhm … you’re right. I added --noconfigure and forgot to mention it here (I followed the CG to be sure I did everything right). > Anyway if I follow your steps but just add --noconfigure it all works > for me. > > Unless anyone else can spot what is going on, perhaps output from your > .configure run might give some clues? See attachment for the full output of ../configure after cleaning up the config files and running ./autogen.sh --noconfigure mkdir build cd build I don’t know what to look for but there is no error message or something else that caught my eye … _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
