Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-19 Thread Jacques Menu
Thanks a lot Werner, works like a charm! JM > Le 19 juil. 2020 à 09:11, Werner LEMBERG a écrit : > > > >> In fact I did the ‘git clone’ afresh, moving aside previous >> attempts. Thus the contents of ‘build’ on both OSes is the result of >> the commands I showed, up to '../configure'. >> >>

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-19 Thread Werner LEMBERG
> In fact I did the ‘git clone’ afresh, moving aside previous > attempts. Thus the contents of ‘build’ on both OSes is the result of > the commands I showed, up to '../configure'. > > That’s why I don’t get what happens… For me, using an up-to-date MacPorts system, compilation of LilyPond from

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Jacques Menu
PS> My goal is to build Lily to do experiments on the Mac, which is much faster and confortable for me to work with, rather that on my Debian virtual machine. > Le 18 juil. 2020 à 17:23, Jacques Menu a écrit : > > Hello Jonas and Werner, > > In fact I did the ‘git clone’ afresh, moving aside p

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Jacques Menu
Hello Jonas and Werner, In fact I did the ‘git clone’ afresh, moving aside previous attempts. Thus the contents of ‘build’ on both OSes is the result of the commands I showed, up to '../configure'. That’s why I don’t get what happens… JM > Le 18 juil. 2020 à 16:46, Werner LEMBERG a écrit :

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Werner LEMBERG
> I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and > Mac OS X 10.14.6 (Mojave). On the latter, I installed Apple’s > XCode, the needed tools in /opt with MacPorts, and the needed fonts > in /opt/local/share/fonts/urw-core35-fonts. You might apply https://github.com/macports/m

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Jonas Hahnfeld
Hi, Am Samstag, den 18.07.2020, 15:14 +0200 schrieb Jacques Menu: > Hello folks, > > I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and Mac OS X > 10.14.6 (Mojave). > On the latter, I installed Apple’s XCode, the needed tools in /opt with > MacPorts, and the needed fonts in /opt

2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Jacques Menu
Hello folks, I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and Mac OS X 10.14.6 (Mojave). On the latter, I installed Apple’s XCode, the needed tools in /opt with MacPorts, and the needed fonts in /opt/local/share/fonts/urw-core35-fonts. Performing the same ‘git clone’ and the

Re: Build problem with fonts

2019-12-09 Thread Federico Bruni
Il giorno lun 9 dic 2019 alle 11:18, Federico Bruni ha scritto: Il giorno lun 9 dic 2019 alle 08:38, Werner LEMBERG ha scritto: Your `t1asm` binary crashes with a segmentation fault, as can be seen in last two lines of `mf2pt1.strace.657213`: --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_M

Re: Build problem with fonts

2019-12-09 Thread Federico Bruni
Il giorno lun 9 dic 2019 alle 08:38, Werner LEMBERG ha scritto: Your `t1asm` binary crashes with a segmentation fault, as can be seen in last two lines of `mf2pt1.strace.657213`: --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x3055683} --- +++ killed by SIGSEGV (core dumped)

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG
>> Please try again with >>strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf >> so that we can see the strace messages from `t1asm` also. Note that >> you will get at least two files called `mf2pt1.strace.X`, where >> `X` is a process ID. >> > > Four log-files were created, and the 3

Re: Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude
Le 08/12/2019 à 18:12, Werner LEMBERG a écrit : Please try again with strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf so that we can see the strace messages from `t1asm` also. Note that you will get at least two files called `mf2pt1.strace.X`, where `X` is a process ID. Four log-

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG
>> Strange indeed. Can you temporarily replace `mf2pt1` with a script >> that calls `strace`? Something like >>strace mf2pt1 ... &> ~/mf2pt1.strace.log >> You could then investigate in more detail which files `mf2pt1` tries >> to open and/or execute. >> > > [jcharles@pc1 mf]$ strace mf2pt

Re: Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude
Le 08/12/2019 à 17:10, Werner LEMBERG a écrit : Strange indeed. Can you temporarily replace `mf2pt1` with a script that calls `strace`? Something like strace mf2pt1 ... &> ~/mf2pt1.strace.log You could then investigate in more detail which files `mf2pt1` tries to open and/or execute. [

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG
> which t1asm > /usr/bin/t1asm > > so I don't see any reason why, just at once, it failed at running… > after a good sleeping night! Strange indeed. Can you temporarily replace `mf2pt1` with a script that calls `strace`? Something like strace mf2pt1 ... &> ~/mf2pt1.strace.log You could the

Re: Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude
Le 08/12/2019 à 16:51, Werner LEMBERG a écrit : Can you execute t1asm? t1asm --help It works either in $HOME or in my compiling folders. Is it in your path that you use for compiling lilypond? which t1asm /usr/bin/t1asm so I don't see any reason why, just at once, it failed at runni

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG
> I notice, upwards in the log, that > > Invoking "t1asm feta11.pt1 feta11.pfb"... > mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find > another way to convert feta11.pt1 to feta11.pfb > > > despite I've t1utils-1.41-1.fc31.x86_64 installed. Can you execute t1asm? t1as

Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude
Hi all, For about two weeks now, I'm unable to build and then merge translation with stable, even after a fresh clone. I cannot believe it has something to do with an upgrade from Fedora 30 to 31. Tail of the log : --8<-- cd ./out && /usr/bin/fontforge -script emmentaler-11.genpe Copyright (c

Re: build problem

2019-07-26 Thread Jean-Charles Malahieude
Le 26/07/2019 à 09:44, Federico Bruni a écrit : Jean-Charles, version 1.0.3 is now available in Fedora 30 repositories. And version 1.1.0 is in rawhide. As I've cloned the repository and built it without any problem, everything is fine. Cheers, Jean-Charles ___

Re: build problem

2019-07-26 Thread Federico Bruni
Il giorno lun 1 lug 2019 alle 8:03, Federico Bruni ha scritto: Yes, I run Fedora 30 since it was released and I can compile lilypond without any problem using the package available in Fedora. I've now built the rpm for version 1.0.3 and it works as well. I'll submit the new version to the Fedo

Re: build problem

2019-06-30 Thread Federico Bruni
Il giorno dom 30 giu 2019 alle 10:45, Jean-Charles Malahieude ha scritto: My first attempts were using the official Fedora package (as I do since one is available), version 1.0.2. Facing this library problem, I've built a package for 1.0.3 and then 1.1.0 which both bump the wall. Unfortunate

Re: build problem

2019-06-30 Thread Jean-Charles Malahieude
Le 30/06/2019 à 11:10, Knut Petersen a écrit : Build it yourself. Building and installing extractpdfmark is an easy an fast task. Cloning the repository, building, testing and installing of extractpdfmark takes less than 20 seconds here: This, as intended, works like a charm, but I was expe

Re: build problem

2019-06-30 Thread Knut Petersen
On 30.06.19 10:45, Jean-Charles Malahieude wrote: Unfortunately, I don't remember if my last merge was just before upgrading to Fedora 30 or not. And Federico, who runs a Fedora 30 as well if I'm not mistaken, pushed on Translation mid-June… Build it yourself. Building and installing extract

Re: build problem

2019-06-30 Thread Jean-Charles Malahieude
Le 30/06/2019 à 02:51, Masamichi Hosoda a écrit : In Fedora 30, I suggest to use extractpdfmark from package, rather than self-built extractpdfmark. https://apps.fedoraproject.org/packages/extractpdfmark If I understand correctly, Fedora 30 has popler-0.73.0 package that has libpoppler.so.84. ht

Re: build problem

2019-06-29 Thread Masamichi Hosoda
> Hello, > > Since I can't get a successful doc-build on my Fedora 30 box, I'm > unable to check doc-changes and merge translation into stable. > > It's the same with extractpdfmark 1.0.2 1.0.3 and 1.1.0 > > log spits: > > extractpdfmark -o ./out-www/collated-files.pdfmark > ./out-www/collated-

build problem

2019-06-29 Thread Jean-Charles Malahieude
Hello, Since I can't get a successful doc-build on my Fedora 30 box, I'm unable to check doc-changes and merge translation into stable. It's the same with extractpdfmark 1.0.2 1.0.3 and 1.1.0 log spits: extractpdfmark -o ./out-www/collated-files.pdfmark ./out-www/collated-files.tmp.pdf extr

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-03 Thread James
Hello On 03/06/2019 12:29, Knut Petersen wrote: Hi Werner! OK.  Do you have time to prepare a patch? No time ... but attached is quick shot. Min version 2.44 seems reasonable as we use it in gub. Knut Thanks https://sourceforge.net/p/testlilyissues/issues/5525/ James ___

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-03 Thread Knut Petersen
Hi Werner! OK. Do you have time to prepare a patch? No time ... but attached is quick shot. Min version 2.44 seems reasonable as we use it in gub. Knut >From 619de1764cd472ec7587f98c34ba7b7e613be93c Mon Sep 17 00:00:00 2001 From: Knut Petersen Date: Mon, 3 Jun 2019 12:30:08 +0200 Subject:

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-03 Thread Werner LEMBERG
> I think it is clear that we really need to test for and link against > the glib-2.0 and gobject-2.0 libraries. OK. Do you have time to prepare a patch? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailma

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-03 Thread Knut Petersen
Hi Werner! I always thought that `pkg-config' resolves dependencies recursively. Even with your `pangoft2.pc' file it should check the dependencies in `pango.fc', right? And there I see Requires: glib-2.0 gobject-2.0 Tumbleweed also moved those dependencies to 'Require.private' ;-) But I g

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-02 Thread Werner LEMBERG
> pkg-config --libs "pangoft2 >= 1.38.0" gives > >-lpangoft2-1.0 -lpango-1.0 -lfontconfig -lfreetype Not for me. I get -L/usr/local/lib64 -lpangoft2-1.0 -lpango-1.0 \ -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype > Weird. Look at /usr/lib64/pkgconfig/pangoft2.pc: > >prefix=/us

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-02 Thread Knut Petersen
Hi Werner! I added libgobject-2.0 to LIBS: "export LIBS='-lglib-2.0 -lgobject-2.0'", and after that building the lilypond executable succeeded again. Hmm. LilyPond doesn't explicitly test for glib; it relies on PANGO_FT2_LIBS, which should always add those two libraries for building the `lilypo

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-01 Thread Werner LEMBERG
> After some time without building lilypond I realized that my > openSuSE Tumbleweed system had changed enough to be unable to build > lilypond with my old and proven script. The problem is that some > required libraries are missing from the g++ command line that should > produce the lilypond ex

Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-05-30 Thread Knut Petersen
Hi everybody! After some time without building lilypond I realized that my openSuSE Tumbleweed system had changed enough to be unable to build lilypond with my old and proven script. The problem is that some required libraries are missing from the g++ command line that should produce the lilyp

Re: Lilypond gcc45 build problem

2010-02-28 Thread Dave Plater
On 02/22/2010 08:52 PM, Jan Nieuwenhuizen wrote: > > Yes... it's always nice to have lily building with the latest and > greatest - although I see that gcc-4.5.0 development currently has > about 250 regressions, half of them serious ones. I'm not sure > if debugging this right now is helpful. > >

Re: Lilypond gcc45 build problem

2010-02-22 Thread Jan Nieuwenhuizen
Op maandag 22-02-2010 om 19:09 uur [tijdzone +0200], schreef Dave Plater: Hi Dave, > lilypond is no longer building for openSUSE Factory due to the switch to > gcc45. I noticed from the git logs that you have worked on > spacing-spanner.cc recently which is where gcc45 fails. Yes, I noticed. I

Re: Local Gub build problem

2008-07-16 Thread John Mandereau
On 2008/07/14 20:17 +, Mark Hanlon wrote: > LILYPOND_REPO_URL=file://localhost/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource > > # ugh - make this automatic. > LILYPOND_DIRRED_BRANCH=localhost/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource/$(LILYPOND_BRANCH) > LILYPOND_FLATTENED_BRA

Local Gub build problem

2008-07-14 Thread Mark Hanlon
Hello, I've been trying to use the local.build file that Han-Wen supplied to do a GUB build of a patched version of lilypond for the music notation project. I have amended the contents of the local.build file to point to the location of my source code which is /home/maz/lilypondbuilds/mygub/gu

source build problem 2.9.24

2006-10-17 Thread Ian Stirling
I asked about this with 2.9.22 and had no answer. On FreeBSD RELEASE-6.1, Failed to open: /usr/X11R6/lib/X11/fonts/bitstream-vera/VeraBd.pfb This file is not in the bitstream-vera on my system. Please, where can I get it or make it? Ian -- ___ li

source build problem 2.9.22

2006-10-12 Thread Ian Stirling
I have the following error trying to build 2.9.22 from source on a FreeBSD 6.1-RELEASE system with bitstream-vera 1.10_2. Cannot open /usr/X11R6/lib/X11/fonts/bitstream-vera/VeraBd.pfb The requested file, VeraBd.pfb, does not exist Open: Failed to open: /usr/X11R6/lib/X11/fonts/bitstream-vera/Ve

Re: About lilypond's build problem with debian

2006-07-25 Thread Thomas Bushnell BSG
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Thomas Bushnell BSG schreef: >> The problem is that lilypond's build system assumes that lilypond is >> already installed on the system. >> >> Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out >> in the thread, it is setting LILYPON

Re: About lilypond's build problem with debian

2006-07-25 Thread Ludovic RESLINGER
Re, I have found why it builed for you and not on my system. The python version installed on my system was a 2.4 version. I had backported on a 2.3 version, and the problem seem solved. It will be interesting to know why there is this problem with new versions of python, because if one day Pytho

Re: About lilypond's build problem with debian

2006-07-25 Thread Han-Wen Nienhuys
Thomas Bushnell BSG schreef: The problem is that lilypond's build system assumes that lilypond is already installed on the system. Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out in the thread, it is setting LILYPONDPREFIX *incorrectly*, and the reason the builds are working

Re: About lilypond's build problem with debian

2006-07-25 Thread Ludovic RESLINGER
On Tue, Jul 25, 2006 at 02:08:03AM -0700, Thomas Bushnell BSG wrote: > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > > Thomas Bushnell BSG schreef: > > > >> I'm distressed that nobody has bothered to fix the bug since then. In > >> the thread on the mailing list you can see that if LILYPONDPRE

Re: About lilypond's build problem with debian

2006-07-25 Thread Thomas Bushnell BSG
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Thomas Bushnell BSG schreef: > >> I'm distressed that nobody has bothered to fix the bug since then. In >> the thread on the mailing list you can see that if LILYPONDPREFIX is >> set correctly, the bug goes away. > > This issue has been addressed in

Re: About lilypond's build problem with debian

2006-07-24 Thread Ludovic RESLINGER
On Sun, Jul 23, 2006 at 12:25:42PM +0200, Han-Wen Nienhuys wrote: > Thomas Bushnell BSG schreef: > > >I'm distressed that nobody has bothered to fix the bug since then. In > >the thread on the mailing list you can see that if LILYPONDPREFIX is > >set correctly, the bug goes away. > > This issue

Re: About lilypond's build problem with debian

2006-07-23 Thread Han-Wen Nienhuys
Thomas Bushnell BSG schreef: I'm distressed that nobody has bothered to fix the bug since then. In the thread on the mailing list you can see that if LILYPONDPREFIX is set correctly, the bug goes away. This issue has been addressed in a more robust manner in the 2.9 series, and I would welco

Re: About lilypond's build problem with debian

2006-07-22 Thread Ludovic RESLINGER
On Fri, Jul 21, 2006 at 04:57:14PM -0700, Thomas Bushnell BSG wrote: > Ludovic RESLINGER <[EMAIL PROTECTED]> writes: > > > I saw in archive some messages about a problem to build lilypond in > > debian unstable. I think this is not a problem of python's version, because > > I tested to build with

Re: About lilypond's build problem with debian

2006-07-21 Thread Thomas Bushnell BSG
Ludovic RESLINGER <[EMAIL PROTECTED]> writes: > I saw in archive some messages about a problem to build lilypond in > debian unstable. I think this is not a problem of python's version, because > I tested to build with python2.4 and python2.5, and the problem stay the > same: > > chmod 755 out/con

Re: About lilypond's build problem with debian

2006-07-20 Thread Ludovic RESLINGER
On Wed, Jul 19, 2006 at 07:47:35PM +0200, Mats Bengtsson wrote: > If you run > scripts/out/convert-ly --help > from the lilypond/ directory, you will get a much more informative > error message that might > help you find out what the problem is. > > /Mats > Hello Thank you for your answer. W

Re: About lilypond's build problem with debian

2006-07-19 Thread Mats Bengtsson
If you run scripts/out/convert-ly --help from the lilypond/ directory, you will get a much more informative error message that might help you find out what the problem is. /Mats Quoting Ludovic RESLINGER <[EMAIL PROTECTED]>: Hello, I saw in archive some messages about a problem to build li

About lilypond's build problem with debian

2006-07-19 Thread Ludovic RESLINGER
Hello, I saw in archive some messages about a problem to build lilypond in debian unstable. I think this is not a problem of python's version, because I tested to build with python2.4 and python2.5, and the problem stay the same: chmod 755 out/convert-ly /usr/bin/perl /home/me/lilypond-2.8.4/buil

Re: cygwin build problem in mf

2005-02-09 Thread Peter Leschev
Wednesday, February 09, 2005 10:42 PM Subject: Re: cygwin build problem in mf Peter Leschev writes: I'm trying to build the latest from CVS under cygwin, and I'm getting the following error. Any ideas? Yes. mv feta11.{pfa,pfb,svg} ./out mv: cannot stat `feta11.{pfa,pfb,svg}&#

Re: cygwin build problem in mf

2005-02-09 Thread Jan Nieuwenhuizen
Peter Leschev writes: > I'm trying to build the latest from CVS under cygwin, and I'm getting > the following error. Any ideas? Yes. > mv feta11.{pfa,pfb,svg} ./out > mv: cannot stat `feta11.{pfa,pfb,svg}': No such file or directory {} is a bashism, use bash as /bin/sh, or try make SHE

cygwin build problem in mf

2005-02-09 Thread Peter Leschev
Hi,           I'm trying to build the latest from CVS under cygwin, and I'm getting the following error. Any ideas?   Regards, Peter     make[1]: Entering directory `/cygdrive/c/sandbox/org/lilypond/lilypond/mf'mftrace --encoding feta11.enc --no-afm -I ./out/ --formats=pfa,pfb,svg feta11mftr

another build problem

2004-10-30 Thread Laura Conrad
Again, Debian, Sid, 2.4.0. rm -f ./out/lexer.dep; DEPENDENCIES_OUTPUT="./out/lexer.dep ./out/lexer.o" g++ -c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out -I../flower/include -I../flower/./out -I../flower/include -O2 -finline-functions -g -pipe -I/usr/include/python2.3 -O

Re: Newbie Alert--build problem CVS

2002-07-16 Thread Zach Brewster-Geisz
Thus spake Christian Hitz: >Am Dienstag den, 16. Juli 2002, um 11:45, schrieb Jan Nieuwenhuizen: >> >>Please send a patch if you get it working, maybe addding small >>comments as above. > >With the attached patch applied to the current CVS, you can build >lilypond on MacOS X (and i hope also on d

Re: Newbie Alert--build problem CVS

2002-07-16 Thread Christian Hitz
Am Dienstag den, 16. Juli 2002, um 11:45, schrieb Jan Nieuwenhuizen: > > Please send a patch if you get it working, maybe addding small > comments as above. With the attached patch applied to the current CVS, you can build lilypond on MacOS X (and i hope also on darwin). Jan: your hint did the

Newbie Alert--build problem CVS

2002-07-16 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Hello. Long time listener, first time caller. > > I get the following error when building from the latest (well, this > morning's) CVS: Thanks for the report ; should be fixed in CVS. > I'm using gcc v. 2.95, building on Apple Darwin 1.4.1. I have the > Fink inst

Re: Newbie Alert--build problem CVS

2002-07-16 Thread Jan Nieuwenhuizen
Zach Brewster-Geisz <[EMAIL PROTECTED]> writes: > Hello. Long time listener, first time caller. Loud and clear, over. > I get the following error when building from the latest (well, this > morning's) CVS: > In file included from note-collision.cc:11: > ../flower/include/drul-array.hh: In ins

Newbie Alert--build problem CVS

2002-07-15 Thread Zach Brewster-Geisz
Hello. Long time listener, first time caller. I get the following error when building from the latest (well, this morning's) CVS: rm -f ./out/note-collision.dep; DEPENDENCIES_OUTPUT="./out/note-collision.dep ./out/note-collision.o" c++ -c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -

Re: build problem with current cvs

2002-07-13 Thread Laura Conrad
> "Han-Wen" == Han-Wen <[EMAIL PROTECTED]> writes: Han-Wen> [EMAIL PROTECTED] writes: >> I just upped CVS, and when I run "make", I get: Han-Wen> run make clean Now I get: makeinfo --output=./out/lilypond.info out/lilypond.nexi out/lilypond.nexi:269: Node `Preface' requires a

build problem with current cvs

2002-07-13 Thread Han-Wen
[EMAIL PROTECTED] writes: > I just upped CVS, and when I run "make", I get: run make clean -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/

build problem with current cvs

2002-07-13 Thread Laura Conrad
I just upped CVS, and when I run "make", I get: rm -f ./out/align-interface.dep; DEPENDENCIES_OUTPUT="./out/align-interface.dep ./out/align-interface.o" c++ -c -DHAVE_CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out -I.././lib/include -I../lib/./out -I.././flower/include -I../flower/./out -