From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>,
broonie@kernel.org, mhocko@suse.cz, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
mm-commits@vger.kernel.org, Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: mmotm 2022-03-30-13-01 uploaded (DWARF error: could not find abbrev number 74)
Date: Thu, 31 Mar 2022 08:07:44 -0700 [thread overview]
Message-ID: <c79266be-06b0-1ac9-c95e-96d0d51e461d@infradead.org> (raw)
In-Reply-To: <20220330200158.2F031C340EC@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
On 3/30/22 13:01, Andrew Morton wrote:
> The mm-of-the-moment snapshot 2022-03-30-13-01 has been uploaded to
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> https://ozlabs.org/~akpm/mmotm/series
on x86_64:
ld: ld: DWARF error: could not find abbrev number 74
or
ld: ld: DWARF error: could not find abbrev number 77
gcc is:
gcc (SUSE Linux) 7.5.0
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-r2608.gz --]
[-- Type: application/gzip, Size: 35216 bytes --]
next prev parent reply other threads:[~2022-03-31 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 20:01 mmotm 2022-03-30-13-01 uploaded Andrew Morton
2022-03-31 6:50 ` mmotm 2022-03-30-13-01 uploaded (kernel/sched/ and sysctls) Randy Dunlap
2022-03-31 23:14 ` Luis Chamberlain
2022-03-31 15:07 ` Randy Dunlap [this message]
2022-03-31 15:50 ` mmotm 2022-03-30-13-01 uploaded (drivers/platform/x86/amd-pmc.o) Randy Dunlap
2022-03-31 18:41 ` Limonciello, Mario
2022-04-01 15:00 ` Hans de Goede
2022-04-01 15:11 ` Limonciello, Mario
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=c79266be-06b0-1ac9-c95e-96d0d51e461d@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).