From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patches being worked on
Date: Mon, 29 Mar 2021 22:22:03 +0100 [thread overview]
Message-ID: <97FDDAFD-CB26-4A34-AB8E-F8936F968CF2@ipfire.org> (raw)
In-Reply-To: <a366e5fa-a456-f75e-5610-5cf8a374ae88@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
Hello,
> On 29 Mar 2021, at 21:46, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael,
>
> On 29/03/2021 22:11, Michael Tremer wrote:
>> Hello,
>>> On 28 Mar 2021, at 09:33, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>
>>> Hi All,
>>>
>>>
>>> For info I am working on the following update patches:-
>>>
>>> bash
>> Could you please update readline together with bash?
>> They belong together.
> I will do that, together with your input in the other email about how to deal with bash.
>>> binutils
>> Peter worked on this before and said the build crashes in various places. There should be something you can use as a start to confirm.
> Yes, I already found issues, which is why it was taken out of the patches I submitted. I will go back and have another look at it.
You can post these things on the list, just for reference or to check if anybody else has an idea. I would like to know what breaks, even if we cannot do something about it without any further and bigger works.
>>> bison
>>> bzip2
>>> diffutils
>>> ed
>>> gawk
>>> lm_sensors
>>> perl
>> Perl might be a massive one because there are so many dependencies that need to be update at the same time. Let me know how this goes :)
> That I have found already. I am currently working on it and struggling a bit. I am making small progress but then hit another issue. My current one is having built it and adjusted mpfire-ipfire to use the correct directory names (based on perl version) I now have a problem at the building cdrom stage which looks to be related to the rootfile. A lot of it seems to be missing including the /usr/bin/perl entries. I will investigate further but may need to come back with the error for advice and guidance.
Yes, it is a lot of try-and-error and very time-consuming :)
-Michael
> Regards,
> Adolf.
>> -Michael
>>> Regards,
>>>
>>> Adolf
>>>
>>> --
>>> Sent from my laptop
>>>
prev parent reply other threads:[~2021-03-29 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 8:33 Adolf Belka
2021-03-28 13:52 ` Adolf Belka
2021-03-29 20:14 ` Michael Tremer
2021-03-29 20:11 ` Michael Tremer
2021-03-29 20:46 ` Adolf Belka
2021-03-29 21:22 ` Michael Tremer [this message]
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=97FDDAFD-CB26-4A34-AB8E-F8936F968CF2@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