From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [chrome-os:chromeos-4.4 1/1] hppa-linux-ld: drivers/built-in.o(.init.text+0x3d6cc): cannot reach 00009552_14523:4177b+0, recompile with -ffunction-sections
Date: Sat, 13 Feb 2021 19:45:27 +0800 [thread overview]
Message-ID: <202102131925.QAOXiymv-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-4.4
head: 16313d2d83c34dc912fd2e33d0525468bf236333
commit: 16313d2d83c34dc912fd2e33d0525468bf236333 [1/1] Merge "CHROMIUM: Merge 'v4.4.257' into chromeos-4.4" into chromeos-4.4
config: parisc-allyesconfig (attached as .config)
compiler: hppa-linux-gcc (GCC) 7.5.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add chrome-os https://chromium.googlesource.com/chromiumos/third_party/kernel
git fetch --no-tags chrome-os chromeos-4.4
git checkout 16313d2d83c34dc912fd2e33d0525468bf236333
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-7.5.0 make.cross ARCH=parisc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> hppa-linux-ld: drivers/built-in.o(.init.text+0x3d6cc): cannot reach 00009552_14523:4177b+0, recompile with -ffunction-sections
>> hppa-linux-ld: drivers/built-in.o(.init.text+0x3d6cc): cannot handle R_PARISC_PCREL17F for hp100_probe1
hppa-linux-ld: final link failed: Bad value
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 44367 bytes --]
reply other threads:[~2021-02-13 11:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202102131925.QAOXiymv-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.