From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem during building of samba on arm builder
Date: Wed, 03 Jul 2024 22:44:16 +0200 [thread overview]
Message-ID: <6ec6379b-6fb5-49f8-a074-f50cccbdcba4@ipfire.org> (raw)
In-Reply-To: <30FFC964-F6D1-4AB7-AB83-C9DD3DB0468A@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
Worked okay this time round.
Samba build took 3.5 hours.
Regards,
Adolf.
On 03/07/2024 11:58, Michael Tremer wrote:
> Hello Adolf,
>
> This happens occasionally that the buildsystem umounts /dev and then nothing will really work any more.
>
> I rebooted the machine and it is back up again.
>
> -Michael
>
>> On 2 Jul 2024, at 15:42, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael and all,
>>
>>
>> I ran the arm builder with the 4.20.2 version of samba to test it out.
>>
>> The build got to building gdb and then failed.
>>
>> Interestingly, the nightly build of arm was successful with the same version of gdb.
>>
>> The build log for gdb is attached. The actual error is at line 618.
>>
>> Another thing I found is that I just tried to go back into the arm builder. I successfully got into people.ipfire.org but then trying to scp into the arm builder failed with the following message.
>>
>> ------------------------------------------
>>
>> ssh bonnietwin(a)arm64-01.zrh.ipfire.org
>> PTY allocation request failed on channel 0
>> Linux arm64-01.zrh.ipfire.org 6.1.0-21-cloud-arm64 #1 SMP Debian 6.1.90-1 (2024-05-03) aarch64
>>
>> The programs included with the Debian GNU/Linux system are free software;
>> the exact distribution terms for each program are described in the
>> individual files in /usr/share/doc/*/copyright.
>>
>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>> permitted by applicable law.
>> /etc/profile.d/Z99-cloud-locale-test.sh: line 14: /dev/null: Permission denied
>>
>> ------------------------------------------
>>
>> Regards,
>>
>> Adolf.
>>
>> <_build.ipfire.gdb.log>
>
next prev parent reply other threads:[~2024-07-03 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 14:42 Adolf Belka
2024-07-03 9:58 ` Michael Tremer
2024-07-03 20:44 ` Adolf Belka [this message]
2024-07-08 16:11 ` Michael Tremer
2024-07-08 19:15 ` Adolf Belka
2024-07-08 19:34 ` Adolf Belka
2024-07-09 21:29 ` Michael Tremer
2024-07-10 9:57 ` Michael Tremer
2024-07-10 10:33 ` Adolf Belka
2024-07-10 12:59 ` Adolf Belka
2024-07-10 13:05 ` Adolf Belka
2024-07-10 13:21 ` Adolf Belka
2024-07-10 14:24 ` Michael Tremer
2024-07-10 16:53 ` Adolf Belka
2024-07-10 18:19 ` Michael Tremer
2024-07-10 21:57 ` 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=6ec6379b-6fb5-49f8-a074-f50cccbdcba4@ipfire.org \
--to=adolf.belka@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