prometheus / prometheus/node_exporter

SmartOS build fail LDFLAGS: -fno-stack-protector -lssp

Open
#1,017 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
13.8k
Forks
2.7k
Avg merge
1d 23h
Merged PRs (30d)
8

Description

Host operating system: output of uname -a

SunOS smartos-fun 5.11 joyent_20180427T013714Z i86pc i386 i86pc Solaris

node_exporter version: output of node_exporter --version

node_exporter, version 0.16.0 (branch: master, revision: ca2fa4684b53d3021ce6f8c98886a1c93767000d)
build user: root@smartos-fun
build date: 20180723-14:09:55
go version: go1.10

node_exporter command line flags

N/A, build issue.

Are you running node_exporter in Docker?

No

What did you do that produced an error?
  1. I created a base-64-lts@17.4.0 image in Triton
  2. Installed build tools pkgin in go gcc49 gmake git
  3. Build node exporter go get github.com/prometheus/node_exporter
What did you expect to see?

A built executable

What did you see instead?
[root@smartos-fun ~]# go get github.com/prometheus/node_exporter
go build github.com/prometheus/node_exporter/collector: invalid flag in #cgo LDFLAGS: -fno-stack-protector

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing go get github.com/prometheus/node_exporter on the reported SmartOS environment with Go 1.10 and the listed build tools. Trace the go build failure reporting the invalid cgo LDFLAGS -fno-stack-protector; done means the node_exporter executable builds successfully on SmartOS.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.