From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: Laszlo KERTESZ <laszlo.kertesz@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Build fails on Debian, kernel 4.20.0-rc4
Date: Sun, 02 Dec 2018 11:10:38 +0000 [thread overview]
Message-ID: <ZXZgXRYJnrxY3Gq_xY8uWt7ZJiY1WguNk-BA-UY67mIJyGtZMGkcU3xr_bOuJ7YCvBtis033v6rcZKGq4VALz1VQYLwHRZjrsGRw-WfKa_I=@protonmail.ch> (raw)
In-Reply-To: <CANcuY=r=6fd+1+4arDi+95+BnWAiQupkT1Zct=Osktf9J4AUcA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 904 bytes --]
On Sunday, December 2, 2018 12:38 AM, Laszlo KERTESZ <laszlo.kertesz@gmail.com> wrote:
> On Sun, Dec 2, 2018 at 1:26 AM Tushar Pankaj <tushar.s.pankaj@gmail.com> wrote:
>
>> Does it have to do with macros.S having a capital S extension?
>>
>> Thanks,
>> Tushar Pankaj
>
> Probably not. I don't have any "arch/x86/kernel/macros.s" file (actually "/usr/src/linux-headers-4.20.0-rc4/arch/x86/kernel/macros.s") at all. In fact neither do i have macros.s or macros.S in previous kernels directories.
And that's why it fails[1]. You have to add "arch/x86/kernel/macros.s" to list of files
to be copied as fedora did. Their first patch contained a typo (capital 'S' instead of 's'[2].
I don' know where debian does handle this though.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1643599
[2] https://src.fedoraproject.org/cgit/rpms/kernel.git/commit/kernel.spec?id=e7c396bbf3cd1563d445275f92b63f8e9da3f13e
[-- Attachment #1.2: Type: text/html, Size: 1744 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-12-02 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 20:56 Laszlo KERTESZ
2018-12-01 21:02 ` QINGWEI ZHANG
2018-12-01 23:22 ` Laszlo KERTESZ
2018-12-01 23:26 ` Tushar Pankaj
2018-12-01 23:38 ` Laszlo KERTESZ
2018-12-02 11:10 ` Jordan Glover [this message]
2018-12-02 10:29 ` John
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='ZXZgXRYJnrxY3Gq_xY8uWt7ZJiY1WguNk-BA-UY67mIJyGtZMGkcU3xr_bOuJ7YCvBtis033v6rcZKGq4VALz1VQYLwHRZjrsGRw-WfKa_I=@protonmail.ch' \
--to=golden_miller83@protonmail.ch \
--cc=laszlo.kertesz@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/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).