public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: The unshared changes give a problem with build after doing git pull on next
Date: Tue, 27 Aug 2024 14:55:49 +0200	[thread overview]
Message-ID: <ad53cd27-4c62-4987-b492-3310c9690ade@ipfire.org> (raw)
In-Reply-To: <70B6F98B-8230-4830-BDC1-7DA5EA984456@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2673 bytes --]

On 27.08.2024 12:01, Michael Tremer wrote:
> Hello,

Hi,

>> On 24 Aug 2024, at 09:33, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>> 
>> On 21.08.2024 16:28, Michael Tremer wrote:
>>> Hello Matthias,
>> 
>> Hi Michael,
>> 
>>> As you might have seen I played around with this all more… There is either a kernel bug, or a bug in unshare which causes these problems…
>>> 
>>> So if we mount /proc manually later this works for me on Ubuntu 22.04 LTS:
>>> 
>>>  https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=8ea702f3f853c4c28a2885dafdcae2e737c0a49b
>>> 
>>> However, there are now some packages which don’t want to build any more.
>>> 
>>> So I would simply suggest to upgrade the kernel on your Ubuntu release like this:
>>> 
>>>  apt install linux-generic-hwe-22.04
>> 
>> Done. Ran without problems.
>> 
>> I'm now on "Linux Devel64-1 6.8.0-40-generic #40~22.04.3-Ubuntu SMP
>> PREEMPT_DYNAMIC..."
>> 
>>> That should allow you to build with the stock make.sh again.
>> 
>> Sorry, but no chance...
>> 
>> Today I tested the hint from "siosios" found in
>> https://community.ipfire.org/t/trying-to-build-188/11999/8
> 
> Are you referring to this?
> 
>    mount -o bind ${BUILD_DIR}/proc ${BUILD_DIR}/proc
> 
> He put this into an unfortunate place and will mount this over and over and over again... but making the empty directory a mount point is something that would acceptable as a workaround.

I tested this again today, but running "./make.sh downloadsrc" ended in
a bunch of error messages: "...mount point does not exist".

So I'm back to my previous solution from
https://community.ipfire.org/t/trying-to-build-188/11999/9

And I found that I only need ONE line:

...
   # If unshare is asked to terminate, terminate all child processes
   "--kill-child"
  )

mount --bind ${BUILD_DIR}/proc ${BUILD_DIR}/proc

 fi

while [ $# -gt 0 ]; do
  case "${1}" in
...

> If you can confirm, I can add this to the code.

Right now I wouldn't add anything. This is too mysterious (to me). Its
working - but I don't know why.

In a few days the LTS-update for Ubuntu 24.04 LTS will be available -
its scheduled for August 29. I'll test this update and then we'll see.

>> Works. Build is running. I'm building 'clamav 1.4.0' right now.
>> 
>> One glitch I found: the new build still has problems identifying the
>> need for customizing new rootfiles(?).
> 
> This might be fixed here:
> 
>   https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=d7ee801712705c97fda658bb71209d814d1db841

Thanks! I'm testing...

Best
Matthias

[Shortened some stuff - again]


  reply	other threads:[~2024-08-27 12:55 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cea14eb2-46f3-424b-8e54-aa9df10c78e3@ipfire.org>
2024-08-08 13:56 ` Fwd: " Matthias Fischer
2024-08-16 15:35 ` Michael Tremer
2024-08-16 16:43   ` Matthias Fischer
2024-08-21 14:28     ` Michael Tremer
2024-08-24  8:33       ` Matthias Fischer
2024-08-27 10:01         ` Michael Tremer
2024-08-27 12:55           ` Matthias Fischer [this message]
2024-08-27 18:03             ` / /
2024-08-28 15:46               ` Michael Tremer
2024-08-28 16:02                 ` / /
2024-08-28 16:30                 ` Matthias Fischer
2024-08-28 17:52                   ` Adolf Belka
2024-08-28 18:28                     ` Matthias Fischer
2024-08-28 19:10                       ` Adolf Belka
2024-08-28 19:13                         ` Adolf Belka
2024-08-29  7:46                         ` Michael Tremer
2024-08-29  0:07                       ` sio /
2024-08-29  7:58                         ` Michael Tremer
2024-08-29 12:00                           ` sio /
2024-08-29 12:17                             ` Michael Tremer
2024-08-29  7:41                       ` Michael Tremer
2024-08-29  7:41                     ` Michael Tremer
2024-08-29  7:39                   ` Michael Tremer
2024-08-30  8:56                     ` Matthias Fischer
     [not found] <184670fa-843f-4d5d-b4c9-1885a995fad8@ipfire.org>
2024-08-06 15:40 ` Michael Tremer
2024-08-08 12:09   ` Adolf Belka
2024-08-08 18:25     ` Adolf Belka
2024-08-08 18:31       ` Michael Tremer
     [not found] <9259926f-7276-450e-9a82-44b3c455f67e@ipfire.org>
2024-08-03  8:54 ` Michael Tremer
2024-08-03  9:39   ` Michael Tremer
     [not found] <2e6a45cb-7c55-4725-81f2-d69f0c7b373f@ipfire.org>
2024-08-02 18:13 ` Michael Tremer
2024-07-26  7:57 Adolf Belka
2024-07-26  8:17 ` Michael Tremer
2024-07-26  8:35   ` Adolf Belka
2024-07-26 12:39     ` Adolf Belka
2024-07-26 13:05       ` Michael Tremer
2024-07-26 14:08         ` Matthias Fischer
2024-07-26 14:18           ` Michael Tremer
2024-07-26 15:06             ` Matthias Fischer
2024-07-26 15:08               ` Michael Tremer
2024-08-02 17:50               ` Michael Tremer

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=ad53cd27-4c62-4987-b492-3310c9690ade@ipfire.org \
    --to=matthias.fischer@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