From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Pending patches for upcoming Core Update 154
Date: Sat, 30 Jan 2021 17:26:32 +0000 [thread overview]
Message-ID: <c0800536-47a7-69e3-f578-9f6a30912f48@ipfire.org> (raw)
In-Reply-To: <0D811C13-DB7D-451B-AEA3-A7B1A09E1FE4@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 5374 bytes --]
Hello Michael,
thank you for trying to reproduce this.
I am currently building current IPFire 2.x "next" with ccache deleted and will report my findings/
progress here. (binutils 2.36 turns out to break so much stuff that I am currently considering not
to send in a patch for it and wait for linux/hyperscan/... to adapt by themselves. Hrmpf.)
Thanks, and best regards,
Peter Müller
> Hi,
>
> I installed a virtual machine with OpenSuSE Leap and I am past the kernel now with my build.
>
> Could you simply remove the ccache directory from your build environment and run your build again?
>
> It does not seem to be the distribution.
>
> -Michael
>
>> On 28 Jan 2021, at 20:20, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Hello *,
>>
>> to keep everyone updated: The root cause for this seems to be a quirk somewhere in the vicinity
>> of objtools (part of the binutils):
>>
>>> arch/x86/crypto/sha512-mb/.tmp_sha512_mb_mgr_flush_avx2.o: warning: objtool: missing symbol for section .text
>>> CC [M] arch/x86/crypto/sha512-mb/sha512_mb_mgr_init_avx2.o
>>> AS [M] arch/x86/crypto/sha512-mb/sha512_mb_mgr_submit_avx2.o
>>> arch/x86/crypto/sha512-mb/.tmp_sha512_mb_mgr_submit_avx2.o: warning: objtool: missing symbol for section .text
>>> AS [M] arch/x86/crypto/sha512-mb/sha512_x4_avx2.o
>>> arch/x86/crypto/sha512-mb/.tmp_sha512_x4_avx2.o: warning: objtool: missing symbol for section .text
>>> LD [M] arch/x86/crypto/sha512-mb/sha512-mb.o
>>> AS arch/x86/entry/entry_64.o
>>> arch/x86/entry/entry_64.S: Assembler messages:
>>> arch/x86/entry/entry_64.S:1642: Warning: no instruction mnemonic suffix given and no register operands; using default for `sysret'
>>> AS arch/x86/entry/thunk_64.o
>>> arch/x86/entry/.tmp_thunk_64.o: warning: objtool: missing symbol table
>>> make[3]: *** [scripts/Makefile.build:427: arch/x86/entry/thunk_64.o] Error 1
>>> make[2]: *** [scripts/Makefile.build:585: arch/x86/entry] Error 2
>>> make[1]: *** [Makefile:1053: arch/x86] Error 2
>>> make[1]: Leaving directory '/usr/src/linux-4.14.212'
>>> make: *** [linux:150: /usr/src/log/linux-4.14.212-ipfire] Error 2
>>
>> Alas, this is currently reproducible on OpenSuSE Leap 15.2 machines trying to build an untouched
>> version of IPFire 2.x (both "next" and "master"). :-/
>>
>> Thanks, and best regards,
>> Peter Müller
>>
>>
>>> Hello development folks,
>>>
>>> Man proposes, God disposes... *sigh*
>>>
>>> Is anyone aware about current kernel in next being un-compilable or am I bumping into some
>>> personal side-effects again?
>>>
>>>> linux (4.14.212) KCFG=[ 3:48 ][ FAIL ]
>>>>
>>>> CC [M] fs/xfs/xfs_inode_item.o
>>>> CC [M] fs/xfs/xfs_refcount_item.o
>>>> CC [M] fs/xfs/xfs_rmap_item.o
>>>> CC [M] fs/xfs/xfs_log_recover.o
>>>> CC [M] fs/xfs/xfs_trans_ail.o
>>>> CC [M] fs/xfs/xfs_trans_bmap.o
>>>> CC [M] fs/xfs/xfs_trans_buf.o
>>>> CC [M] fs/xfs/xfs_trans_extfree.o
>>>> CC [M] fs/xfs/xfs_trans_inode.o
>>>> CC [M] fs/xfs/xfs_trans_refcount.o
>>>> CC [M] fs/xfs/xfs_trans_rmap.o
>>>> CC [M] fs/xfs/xfs_dquot.o
>>>> CC [M] fs/xfs/xfs_dquot_item.o
>>>> fs/xfs/.tmp_xfs_trans_inode.o: warning: objtool: missing symbol for section .text
>>>> CC [M] fs/xfs/xfs_trans_dquot.o
>>>> CC [M] fs/xfs/xfs_qm_syscalls.o
>>>> CC [M] fs/xfs/xfs_qm_bhv.o
>>>> fs/xfs/.tmp_xfs_trans_dquot.o: warning: objtool: missing symbol for section .text
>>>> CC [M] fs/xfs/xfs_qm.o
>>>> CC [M] fs/xfs/xfs_quotaops.o
>>>> fs/xfs/.tmp_xfs_qm_bhv.o: warning: objtool: missing symbol for section .text
>>>> CC [M] fs/xfs/xfs_rtalloc.o
>>>> fs/xfs/.tmp_xfs_dquot.o: warning: objtool: missing symbol for section .init.text
>>>> CC [M] fs/xfs/xfs_acl.o
>>>> CC [M] fs/xfs/xfs_sysctl.o
>>>> CC [M] fs/xfs/xfs_ioctl32.o
>>>> LD [M] fs/xfs/xfs.o
>>>> AR fs/built-in.o
>>>> make[1]: Leaving directory '/usr/src/linux-4.14.212'
>>>> make: *** [linux:149: /usr/src/log/linux-4.14.212-ipfire] Error 2
>>>
>>> Unfortunately, ~/devel/ipfire-2.x/log/_build.ipfire.log does not contain further information regarding
>>> the problem. Having had some issues with a too old kernel on my workstation, this should now be fine again:
>>>
>>>> user(a)machine:~/devel/ipfire-2.x> uname -a
>>>> Linux machine 5.3.18-lp152.60-default #1 SMP Tue Jan 12 23:10:31 UTC 2021 (9898712) x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> Am I missing something? If yes, could somebody please enlighten my tired brain? :-)
>>>
>>> Thanks, and best regards,
>>> Peter Müller
>>>
>>>> Hello *,
>>>>
>>>> to avoid redundancies: I am currently working on Postfix 3.5.9 and (more important) sudo
>>>> 1.9.5p2 for upcoming Core Update 154. Both fix some security issues; I am pretty sure you
>>>> have heard of CVE-2021-3156 affecting the latter by now.
>>>>
>>>> There might be some minor stuff (USB/PCI database files, etc.) to do as well, but I have
>>>> not checked that, yet. :-)
>>>>
>>>> Thanks, and best regards,
>>>> Peter Müller
>>>>
>
next prev parent reply other threads:[~2021-01-30 17:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 17:15 Peter Müller
2021-01-27 19:04 ` Peter Müller
2021-01-27 19:13 ` Adolf Belka
2021-01-27 19:58 ` Peter Müller
2021-01-27 20:05 ` Adolf Belka
2021-01-28 20:20 ` Peter Müller
2021-01-30 16:29 ` Michael Tremer
2021-01-30 17:26 ` Peter Müller [this message]
2021-02-01 11:17 ` Michael Tremer
2021-01-30 13:00 ` Matthias Fischer
2021-01-30 13:08 ` Peter Müller
2021-01-30 13:51 ` Adolf Belka
2021-01-30 16:52 ` Adolf Belka
[not found] <26ED65B8-154A-4476-B9E6-7DCD58078E0C@gmail.com>
2021-02-05 11:10 ` Michael Tremer
2021-02-05 11:38 ` Adolf Belka
2021-02-05 16:19 ` Michael Tremer
2021-02-05 17:31 ` Adolf Belka
2021-02-05 17:46 ` Michael Tremer
2021-02-05 17:59 ` Adolf Belka
[not found] <AC2550F9-7FCE-4533-90BF-B8E46F825D8E@gmail.com>
2021-02-05 8:32 ` Adolf Belka
2021-02-05 11:10 ` 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=c0800536-47a7-69e3-f578-9f6a30912f48@ipfire.org \
--to=peter.mueller@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