All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Curtis Malainey <cujomalainey@google.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Dylan Reid <dgreid@google.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Guenter Roeck <groeck@google.com>
Subject: Re: Cannot build broadwell on for-5.3
Date: Wed, 22 May 2019 16:44:08 +0200	[thread overview]
Message-ID: <s5hwoii1rd3.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAOReqxjQAya8GQ4bOSBfTBHwXd38c33pOMc35rrSj4O4jMaMSQ@mail.gmail.com>

On Wed, 22 May 2019 01:37:39 +0200,
Curtis Malainey wrote:
> 
> It appears the for-5.3 branch had some broken commits pulled in at
> 1c7c3237c0cc4ad3c7b0df458290c8e2a652f178 ("Merge tag 'v5.2-rc1' into
> asoc-5.3 ")
> 
> building for the pixelbook I get the following build errors:
> 
> Invalid absolute R_X86_64_32S relocation: _etext
> make[3]: *** [/mnt/host/source/src/third_party/kernel/v4.14/arch/x86/boot/compressed/Makefile:130:
> arch/x86/boot/compressed/vmlinux.relocs] Error 1
> make[3]: *** Deleting file 'arch/x86/boot/compressed/vmlinux.relocs'
> 
> Mainline is still broken as well. Not sure how to propagate this up to
> the responsible parties, figured I would start a discussion here
> first. I am also open to suggestions if there is a chance I am missing
> something.

Looks like some leftover interfering the build.
Try to cleanup your work directory, e.g. make distclean and rebuild.


HTH,

Takashi

  reply	other threads:[~2019-05-22 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 23:37 Cannot build broadwell on for-5.3 Curtis Malainey
2019-05-22 14:44 ` Takashi Iwai [this message]
2019-05-22 15:21   ` Pierre-Louis Bossart
2019-05-22 18:30     ` Curtis Malainey
2019-05-27 17:24       ` Guenter Roeck
2019-05-28 16:21         ` Curtis Malainey

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=s5hwoii1rd3.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cujomalainey@google.com \
    --cc=dgreid@google.com \
    --cc=groeck@google.com \
    --cc=pierre-louis.bossart@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.