Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-09-11
Date: Wed, 23 Sep 2020 14:21:58 +0200	[thread overview]
Message-ID: <20200923142158.7383c841@windsurf> (raw)
In-Reply-To: <CA+h8R2qENZw1QQKcW628FCHf-tS7JHRrNPa4NMV7QUGE=RKFrg@mail.gmail.com>

Hello,

On Sat, 12 Sep 2020 00:18:34 -0700
Christian Stewart <christian@paral.in> wrote:

> I think host-go always fails on mips64, due to:
> 
> tmp/go-link-094754572/go.o: in function `internal/cpu.Initialize':
> /srv/storage/autobuild/run/instance-3/output-1/host/lib/go/src/internal/cpu/cpu.go:137:(.text+0x14):
> relocation R_MIPS_26 against `a local symbol' cannot be used when
> making a shared object; recompile with -fPIC
> 
> Not familiar with mips - is this something with cflags? Need -fPIC
> here for position-independent code conditional on mips?

It's difficult to really say as there's not much output from how
host-go is building the target libraries. However, everything that goes
into a shared library indeed needs to be built with -fPIC, and MIPS is
particularly picky about this.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2020-09-23 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5f5c7475.1c69fb81.de413.a4f5SMTPIN_ADDED_MISSING@mx.google.com>
2020-09-12  7:18 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2020-09-11 Christian Stewart
2020-09-23 12:21   ` Thomas Petazzoni [this message]

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=20200923142158.7383c841@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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