<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Hi Ekin,</div><div><br></div><div>I recently encountered this as well. You may need to source either go.sh or go.csh in /etc/profile.d, or get a new login shell.</div><div><br></div><div>Best,</div><div>Jason</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Sprint Phone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Ekin Akoglu <ekinakoglu@tutanota.com> </div><div>Date: 10/17/18 8:42 AM (GMT-05:00) </div><div>To: slackbuilds-users@slackbuilds.org </div><div>Subject: [Slackbuilds-users] runc does not build </div><div><br></div></div>
<div>Hi,</div><div><br></div><div>runc build quits with the error below. Do you have an idea? I tried with sbopkg and then directly with the SlackBuild script but both did not work.</div><br><div>go build -buildmode=pie -ldflags "-X main.gitCommit=4fc53a81fb7c994640722ac585fa9ca548971871 -X main.version=1.0.0-rc5 " -tags "seccomp" -o runc .<br>flag provided but not defined: -buildmode<br>usage: build [-o output] [-i] [build flags] [packages]<br><br>Build compiles the packages named by the import paths,<br>along with their dependencies, but it does not install the results.<br><br>If the arguments are a list of .go files, build treats them as a list<br>of source files specifying a single package.<br><br>When the command line specifies a single main package,<br>build writes the resulting executable to output.<br>Otherwise build compiles the packages but discards the results,<br>serving only as a check that the packages can be built.<br><br>The -o flag specifies the output file name. If not specified, the<br>output file name depends on the arguments and derives from the name<br>of the package, such as p.a for package p, unless p is 'main'. If<br>the package is main and file names are provided, the file name<br>derives from the first file name mentioned, such as f1 for 'go build<br>f1.go f2.go'; with no files provided ('go build'), the output file<br>name is the base name of the containing directory.<br><br>The -i flag installs the packages that are dependencies of the target.<br><br>The build flags are shared by the build, clean, get, install, list, run,<br>and test commands:<br><br> -a<br> force rebuilding of packages that are already up-to-date.<br> In Go releases, does not apply to the standard library.<br> -n<br> print the commands but do not run them.<br> -p n<br> the number of builds that can be run in parallel.<br> The default is the number of CPUs available.<br> -race<br> enable data race detection.<br> Supported only on linux/amd64, freebsd/amd64, darwin/amd64 and windows/amd64.<br> -v<br> print the names of packages as they are compiled.<br> -work<br> print the name of the temporary work directory and<br> do not delete it when exiting.<br> -x<br> print the commands.<br><br> -ccflags 'arg list'<br> arguments to pass on each 5c, 6c, or 8c compiler invocation.<br> -compiler name<br> name of compiler to use, as in runtime.Compiler (gccgo or gc).<br> -gccgoflags 'arg list'<br> arguments to pass on each gccgo compiler/linker invocation.<br> -gcflags 'arg list'<br> arguments to pass on each 5g, 6g, or 8g compiler invocation.<br> -installsuffix suffix<br> a suffix to use in the name of the package installation directory,<br> in order to keep output separate from default builds.<br> If using the -race flag, the install suffix is automatically set to race<br> or, if set explicitly, has _race appended to it.<br> -ldflags 'flag list'<br> arguments to pass on each 5l, 6l, or 8l linker invocation.<br> -tags 'tag list'<br> a list of build tags to consider satisfied during the build.<br> For more information about build tags, see the description of<br> build constraints in the documentation for the go/build package.<br><br>The list flags accept a space-separated list of strings. To embed spaces<br>in an element in the list, surround it with either single or double quotes.<br><br>For more about specifying packages, see 'go help packages'.<br>For more about where packages and binaries are installed,<br>run 'go help gopath'. For more about calling between Go and C/C++,<br>run 'go help c'.<br><br>See also: go install, go get, go clean.<br>Makefile:30: recipe for target 'runc' failed<br>make: *** [runc] Error 2<br></div><div><br></div>Best,<div><br></div><div>Ekin</div><div><br></div><div>
--
</div>
Securely sent with Tutanota. Claim your encrypted mailbox today!
<br>
<a href="https://tutanota.com" target="_blank" rel="noopener noreferrer">https://tutanota.com</a> </body></html>