From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: telegraf: update to 1.18.3
Date: Tue, 25 May 2021 19:19:43 +0200 [thread overview]
Message-ID: <20210525171943.eiUck2OZelEN5jUxCRMNLF1mGO2JtX5m1xNN4hbKReI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31116@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/31116#issuecomment-848063725
Comment:
Besides segfaulting the compiler for ARM targets, looks good:
```
/usr/lib/go/pkg/tool/linux_amd64/link -o $WORK/b001/exe/a.out -importcfg $WORK/b001/importcfg.link -buildmode=exe -buildid=s9-UTy9Bz5UB1geuAmIY/hP_SdF5FK7RIvyEpJIjN/FIOn9d4r6AmbA-W9Gigd/s9-UTy9Bz5UB1geuAmIY -X main.version=1.18.3 -extld=armv7l-linux-gnueabihf-gcc $WORK/b001/_pkg_.a
# github.com/influxdata/telegraf/cmd/telegraf
net(.text): direct call too far: .plt a6878e
net(.text): direct call too far: .plt a68783
net(.text): direct call too far: .plt a6876a
net(.text): direct call too far: .plt a6875b
net(.text): direct call too far: .plt a68759
net(.text): direct call too far: .plt a68752
net(.text): direct call too far: .plt a6874f
net(.text): direct call too far: .plt a6873a
runtime/cgo(.text): direct call too far: .plt a68728
runtime/cgo(.text): direct call too far: .plt a68726
runtime/cgo(.text): direct call too far: .plt a68726
runtime/cgo(.text): direct call too far: .plt a68728
runtime/cgo(.text): direct call too far: .plt a68719
runtime/cgo(.text): direct call too far: .plt a68715
runtime/cgo(.text): direct call too far: .plt a68711
runtime/cgo(.text): direct call too far: .plt a68700
runtime/cgo(.text): direct call too far: .plt a686ed
runtime/cgo(.text): direct call too far: .plt a686f5
runtime/cgo(.text): direct call too far: .plt a686ec
runtime/cgo(.text): direct call too far: .plt a686df
runtime/cgo(.text): direct call too far: .plt a686e1
/usr/lib/go/pkg/tool/linux_amd64/link: too many errors
unexpected fault address 0x7f8905077000
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x1 addr=0x7f8905077000 pc=0x46dde1]
```
@the-maldridge looks ok?
next prev parent reply other threads:[~2021-05-25 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 17:11 [PR PATCH] " damadmai
2021-05-25 17:12 ` damadmai
2021-05-25 17:19 ` ericonr [this message]
2021-06-07 14:12 ` ericonr
2021-06-11 19:02 ` [PR PATCH] [Updated] " damadmai
2021-06-11 19:14 ` damadmai
2021-06-12 1:57 ` [PR PATCH] [Closed]: " ericonr
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=20210525171943.eiUck2OZelEN5jUxCRMNLF1mGO2JtX5m1xNN4hbKReI@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 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).