On 15/11/2010 10:54 PM, Patrick McCarty wrote:
Hi Julien,
On 2010-11-15, Julien Rioux wrote:
On 15/11/2010 2:59 PM, Patrick McCarty wrote:
Compiling with debug flags*might* help to narrow down the issue. The
easiest way to compile without optimization is by running autogen.sh
like so
./a
Hi Julien,
On 2010-11-15, Julien Rioux wrote:
> On 15/11/2010 2:59 PM, Patrick McCarty wrote:
> >Compiling with debug flags*might* help to narrow down the issue. The
> >easiest way to compile without optimization is by running autogen.sh
> >like so
> >
> > ./autogen.sh --disable-optimising
>
On 15/11/2010 2:59 PM, Patrick McCarty wrote:
Compiling with debug flags*might* help to narrow down the issue. The
easiest way to compile without optimization is by running autogen.sh
like so
./autogen.sh --disable-optimising
I have done this now, and get the problem again, with little mo
On 2010-11-15, Julien Rioux wrote:
> On 13/11/2010 4:51 PM, Patrick McCarty wrote:
> > If you want to start again with a pristine git checkout (I don't
> > know if this is in the Contributor's Guide yet), the following
> > command sequence usually works for me.
> >
> >make doc-clean
> >mak
Hi Patrick,
On 15/11/2010 2:59 PM, Patrick McCarty wrote:
That being said, this could be a problem with Guile on Ubuntu. As an
additional test, I would try compiling/installing Guile 1.8.7 from
scratch to see if this solves the problem.
I won't try this now, don't have much time.
Can you s
On 2010-11-15, Julien Rioux wrote:
> On 15/11/2010 2:59 PM, Patrick McCarty wrote:
>
> > Can you send the output of running `./autogen.sh --disable-optimising' ?
> > It would be nice to compare that with my output.
> >
>
> Log attached. I'm recompiling at the moment. Will this give me a
> more ve
On 13/11/2010 4:51 PM, Patrick McCarty wrote:
If you want to start again with a pristine git checkout (I don't know
if this is in the Contributor's Guide yet), the following command
sequence usually works for me.
make doc-clean
make distclean
git clean -f -x
Then proceed with ./autogen
Hi,
Sorry for the delay.
On 2010-11-04, Julien Rioux wrote:
> On 04/11/2010 7:34 PM, Patrick McCarty wrote:
> >Are you compiling LilyPond from scratch
>
> by the way for my builds initially I did
>
> git clone git://git.sv.gnu.org/lilypond.git lilypond
> ./autogen.sh
> ./configure.sh
> make
> s
On 04/11/2010 7:34 PM, Patrick McCarty wrote:
Are you compiling LilyPond from scratch
by the way for my builds initially I did
git clone git://git.sv.gnu.org/lilypond.git lilypond
./autogen.sh
./configure.sh
make
sudo make install
Since then I have been doing
git pull
make
sudo make install
On 04/11/2010 7:34 PM, Patrick McCarty wrote:
Are you compiling LilyPond from scratch and using Guile 1.9, by chance?
Sorry that I didn't mention it originally.
I'm compiling the git master from
git://git.sv.gnu.org/lilypond.git
I am running ubuntu 10.10 and installed the dependencies with
a
On Tue, Nov 2, 2010 at 3:57 PM, Julien Rioux wrote:
>
> I've found a strange behaviour using lilypond-book --safe on a lytex file:
> With multiple snippets each containing one \fret-diagram-x markup command,
> compilation works for the first snippet but fails on the next one. Then if
> you run lil
Hi,
I've found a strange behaviour using lilypond-book --safe on a lytex
file: With multiple snippets each containing one \fret-diagram-x markup
command, compilation works for the first snippet but fails on the next
one. Then if you run lilypond-book --safe a second time, it will
successfully
12 matches
Mail list logo
