On 05.02.19 08:40, Knut Petersen wrote:
On 04.02.19 15:29, Alexander Kobel wrote:
Remote debugging... Perfectly correct, here you are.
Thanks.
The file /usr/lib/ld-linux-x86-64.so.2 is used instead of the expected
/home/akobel/gub/gub/target/linux-64/root/usr/lib/ld-linux-x86-64.so.2.
Coul
On 04.02.19 15:29, Alexander Kobel wrote:
Remote debugging... Perfectly correct, here you are.
Thanks.
The file /usr/lib/ld-linux-x86-64.so.2 is used instead of the expected
/home/akobel/gub/gub/target/linux-64/root/usr/lib/ld-linux-x86-64.so.2.
Could you please execute
ls -l `find -L /l
On 05.02.19 00:36, Karlin High wrote:
On 1/29/2019 3:19 AM, Knut Petersen wrote:
lilypond-2.21.0-1.freebsd-x86.sh
Intel Core i5-3450 3.10 GHz
Windows 7 Pro 64-bit SP1
VirtualBox 5.2.22r126460
VM with 2 cores and 4 GB RAM
$ uname -a
FreeBSD freebsd32-vbox 12.0-RELEASE FreeBSD 12.0-RELEASE r3416
On 1/29/2019 3:19 AM, Knut Petersen wrote:
> lilypond-2.21.0-1.freebsd-x86.sh
Intel Core i5-3450 3.10 GHz
Windows 7 Pro 64-bit SP1
VirtualBox 5.2.22r126460
VM with 2 cores and 4 GB RAM
$ uname -a
FreeBSD freebsd32-vbox 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC i386
# pkg install compat6
Hi Alexander!
The argumens given are ok. As usual
mkdir -p STRACE
strace -v -f -ff -s 1 -o STRACE/TP bin/gub --fresh linux-64::guile
will help to identify the problem.
hm, that gives appx. 2 GB of traces, and I'm not sure which process' trace I
should look at. Nothing segfaults
Hi,
On 02.02.19 10:27, Knut Petersen wrote:
On 01.02.19 15:06, Alexander Kobel wrote:
On 01.02.19 14:51, Alexander Kobel wrote:
GUB-bing further down the road now...
Hrmpf, back here sooner than I hoped.
Guile barfed - see the attached log.
libtool: link: x86_64-linux-gcc -g -O2 -Wall -Wmis
Hello,
Here is the current patch countdown list. The next countdown will be on
February 7th
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push:
5469 Add `TEX` environemnt variable for texi2pdf - Masamichi Hoso
