[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: unusable backtrace

From: David Kastrup
Subject: Re: unusable backtrace
Date: Sun, 27 Mar 2022 12:01:06 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)

Werner LEMBERG <> writes:

>>> * The compilation output says, for example,
>>>   ```
>>>   ;;; compiling 
>>> /home/wl/lilypond/out/share/lilypond/current/scm/lily/graphviz.scm
>>>   ;;; compiled
>>> /home/wl/lilypond/out/share/lilypond/current/guile/ccache/2.2-LE-8-3.A/home/wl/lilypond/scm/graphviz.scm.go
>>>   ```
>>>   This is strange: What does '2.2-LE-8-3.A' mean?
>> 2.2 would likely be the major version, LE little endian, 8 could be
>> the cell size and, well, whatever.  Basically the path encodes the
>> details of the bytecode architecture, and then the source path.
> Thanks.  While this sounds useful, ...
>>>   Why do I get two paths concatenated?
>> Because the first path indicates the architecture and involved
>> executable, and the second path indicates the source path of the
>> compiled file.
> ... it is a complete madness to *concatenate* these details into a
> crazy, long string that resembles a path but shows wrong directories.

How does it show wrong directories after resolving symbolic links?

> I'm sure there is a bug somewhere (or I'm doing something wrong).

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]