unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Olivier Dion via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>, 53324@debbugs.gnu.org
Subject: [bug#53324] [PATCH] gnu: Add uftrace.
Date: Mon, 17 Jan 2022 16:55:29 -0500	[thread overview]
Message-ID: <87ee56vxgu.fsf@laura> (raw)
In-Reply-To: <233bfd5965974c3f33639d28e67210f2462e028b.camel@telenet.be>

On Mon, 17 Jan 2022, Maxime Devos <maximedevos@telenet.be> wrote:
> Olivier Dion schreef op ma 17-01-2022 om 16:02 [-0500]:
>> On Mon, 17 Jan 2022, Maxime Devos <maximedevos@telenet.be> wrote:
>>
>> In the mean time, would you have an idea on how to fix __FILE__ for
>> the build?  uftrace uses it for logging and it ends up expanding to
>> `/tmp/guix-build*/source/*`.  I tried to change the `srcdir` in the
>> various Makefile without much success.
>> 
>
> Maybe uftrace supports out-of-tree builds?  Also, does uftrace try to
> read /tmp/guix-build*, or does only the file name appear in
> backtraces?  If the latter, it is presumably not much of a problem.
> If it is, maybe out-of-tree builds could help.  Automake supports
> out-of-tree builds, but I don't know if uftrace's build system does.

It does support out-of-tree build juste like autotool.  The configure
script however does `readlink -f $(dirname $0)` for its `srcdir`.

For example, even if I build at `/tmp/uftrace` where the configure
script is at /home/old/documents/polymtl/bmi/uftrace, I will get
--------------------------------------------------------------------------------
`uftrace:/home/old/documents/polymtl/bmi/uftrace/cmds/record.c:1571:find_in_path`
--------------------------------------------------------------------------------
at runtime.

-- 
Olivier Dion
Polymtl




  reply	other threads:[~2022-01-17 21:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 19:20 [bug#53324] [PATCH] gnu: Add uftrace Olivier Dion via Guix-patches via
2022-01-17 19:34 ` Maxime Devos
2022-01-20 14:10   ` Ludovic Courtès
2022-01-20 16:50     ` Maxime Devos
2022-01-17 19:39 ` Maxime Devos
2022-01-17 21:02   ` Olivier Dion via Guix-patches via
2022-01-17 21:37     ` Maxime Devos
2022-01-17 21:55       ` Olivier Dion via Guix-patches via [this message]
2022-01-18  7:58         ` Maxime Devos
2022-01-17 21:25 ` [bug#53324] [PATCH v2] " Olivier Dion via Guix-patches via
2022-01-20 14:27   ` bug#53324: [PATCH] " Ludovic Courtès
2022-01-20 14:33     ` [bug#53324] " Olivier Dion via Guix-patches via

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ee56vxgu.fsf@laura \
    --to=guix-patches@gnu.org \
    --cc=53324@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=olivier.dion@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).