From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Results from latest test of pakfire-builder
Date: Mon, 30 Oct 2023 10:01:57 +0000 [thread overview]
Message-ID: <3AA5C9DC-1911-46CF-9E38-B8B6813D6797@ipfire.org> (raw)
In-Reply-To: <0d85db99-7807-45f7-96e1-8455b411f27f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]
Hello Adolf,
Thanks for giving this a try. Is there anything in the logs?
You can add —-debug to get some more output.
Best,
-Michael
> On 29 Oct 2023, at 13:23, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi All,
>
> I updated my pakfire branch by doing a git pull with all the latest changes and built everything again.
>
> Then tested out by running sudo pakfire-builder build beep/beep.nm
>
> Result was again just going to the prompt with nothing happening.
>
> Ran the commands with gdb and got following result.
>
> sudo gdb pakfire-builder
> GNU gdb (GDB) 13.2
> Copyright (C) 2023 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-pc-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <https://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from pakfire-builder...
> (gdb) run build beep/beep.nm
> Starting program: /usr/bin/pakfire-builder build beep/beep.nm
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/usr/lib/libthread_db.so.1".
> [New Thread 0x7ffff57dd6c0 (LWP 12756)]
> [Thread 0x7ffff57dd6c0 (LWP 12756) exited]
> [Inferior 1 (process 12752) exited with code 0377]
> (gdb)
>
>
> Regards,
> Adolf.
>
> --
> Sent from my laptop
>
next prev parent reply other threads:[~2023-10-30 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 13:23 Adolf Belka
2023-10-30 10:01 ` Michael Tremer [this message]
2023-10-30 17:56 ` Adolf Belka
2023-11-02 8:25 ` Michael Tremer
2023-11-02 14:24 ` Adolf Belka
2023-11-03 15:05 ` Michael Tremer
2023-11-03 19:13 ` Adolf Belka
2023-11-27 8:54 ` Adolf Belka
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AA5C9DC-1911-46CF-9E38-B8B6813D6797@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox