Vincent Batts
2018-11-14 04:23:20 UTC
correct. The upstream recommends building with the go compiler, rather
than gcc-go.
vb
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
than gcc-go.
vb
Hi Ekin,
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.
Best,
Jason
Sent from my Sprint Phone.
-------- Original message --------
Date: 10/17/18 8:42 AM (GMT-05:00)
Subject: [Slackbuilds-users] runc does not build
Hi,
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.
go build -buildmode=pie -ldflags "-X
main.gitCommit=4fc53a81fb7c994640722ac585fa9ca548971871 -X
main.version=1.0.0-rc5 " -tags "seccomp" -o runc .
flag provided but not defined: -buildmode
usage: build [-o output] [-i] [build flags] [packages]
Build compiles the packages named by the import paths,
along with their dependencies, but it does not install the results.
If the arguments are a list of .go files, build treats them as a list
of source files specifying a single package.
When the command line specifies a single main package,
build writes the resulting executable to output.
Otherwise build compiles the packages but discards the results,
serving only as a check that the packages can be built.
The -o flag specifies the output file name. If not specified, the
output file name depends on the arguments and derives from the name
of the package, such as p.a for package p, unless p is 'main'. If
the package is main and file names are provided, the file name
derives from the first file name mentioned, such as f1 for 'go build
f1.go f2.go'; with no files provided ('go build'), the output file
name is the base name of the containing directory.
The -i flag installs the packages that are dependencies of the
target.
The build flags are shared by the build, clean, get, install, list,
run,
-a
force rebuilding of packages that are already up-to-date.
In Go releases, does not apply to the standard library.
-n
print the commands but do not run them.
-p n
the number of builds that can be run in parallel.
The default is the number of CPUs available.
-race
enable data race detection.
Supported only on linux/amd64, freebsd/amd64, darwin/amd64
and windows/amd64.
-v
print the names of packages as they are compiled.
-work
print the name of the temporary work directory and
do not delete it when exiting.
-x
print the commands.
-ccflags 'arg list'
arguments to pass on each 5c, 6c, or 8c compiler invocation.
-compiler name
name of compiler to use, as in runtime.Compiler (gccgo or
gc).
-gccgoflags 'arg list'
arguments to pass on each gccgo compiler/linker invocation.
-gcflags 'arg list'
arguments to pass on each 5g, 6g, or 8g compiler invocation.
-installsuffix suffix
a suffix to use in the name of the package installation
directory,
in order to keep output separate from default builds.
If using the -race flag, the install suffix is automatically
set to race
or, if set explicitly, has _race appended to it.
-ldflags 'flag list'
arguments to pass on each 5l, 6l, or 8l linker invocation.
-tags 'tag list'
a list of build tags to consider satisfied during the build.
For more information about build tags, see the description of
build constraints in the documentation for the go/build
package.
The list flags accept a space-separated list of strings. To embed
spaces
in an element in the list, surround it with either single or double
quotes.
For more about specifying packages, see 'go help packages'.
For more about where packages and binaries are installed,
run 'go help gopath'. For more about calling between Go and C/C++,
run 'go help c'.
See also: go install, go get, go clean.
Makefile:30: recipe for target 'runc' failed
make: *** [runc] Error 2
Best,
Ekin
--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com
_______________________________________________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.
Best,
Jason
Sent from my Sprint Phone.
-------- Original message --------
Date: 10/17/18 8:42 AM (GMT-05:00)
Subject: [Slackbuilds-users] runc does not build
Hi,
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.
go build -buildmode=pie -ldflags "-X
main.gitCommit=4fc53a81fb7c994640722ac585fa9ca548971871 -X
main.version=1.0.0-rc5 " -tags "seccomp" -o runc .
flag provided but not defined: -buildmode
usage: build [-o output] [-i] [build flags] [packages]
Build compiles the packages named by the import paths,
along with their dependencies, but it does not install the results.
If the arguments are a list of .go files, build treats them as a list
of source files specifying a single package.
When the command line specifies a single main package,
build writes the resulting executable to output.
Otherwise build compiles the packages but discards the results,
serving only as a check that the packages can be built.
The -o flag specifies the output file name. If not specified, the
output file name depends on the arguments and derives from the name
of the package, such as p.a for package p, unless p is 'main'. If
the package is main and file names are provided, the file name
derives from the first file name mentioned, such as f1 for 'go build
f1.go f2.go'; with no files provided ('go build'), the output file
name is the base name of the containing directory.
The -i flag installs the packages that are dependencies of the
target.
The build flags are shared by the build, clean, get, install, list,
run,
-a
force rebuilding of packages that are already up-to-date.
In Go releases, does not apply to the standard library.
-n
print the commands but do not run them.
-p n
the number of builds that can be run in parallel.
The default is the number of CPUs available.
-race
enable data race detection.
Supported only on linux/amd64, freebsd/amd64, darwin/amd64
and windows/amd64.
-v
print the names of packages as they are compiled.
-work
print the name of the temporary work directory and
do not delete it when exiting.
-x
print the commands.
-ccflags 'arg list'
arguments to pass on each 5c, 6c, or 8c compiler invocation.
-compiler name
name of compiler to use, as in runtime.Compiler (gccgo or
gc).
-gccgoflags 'arg list'
arguments to pass on each gccgo compiler/linker invocation.
-gcflags 'arg list'
arguments to pass on each 5g, 6g, or 8g compiler invocation.
-installsuffix suffix
a suffix to use in the name of the package installation
directory,
in order to keep output separate from default builds.
If using the -race flag, the install suffix is automatically
set to race
or, if set explicitly, has _race appended to it.
-ldflags 'flag list'
arguments to pass on each 5l, 6l, or 8l linker invocation.
-tags 'tag list'
a list of build tags to consider satisfied during the build.
For more information about build tags, see the description of
build constraints in the documentation for the go/build
package.
The list flags accept a space-separated list of strings. To embed
spaces
in an element in the list, surround it with either single or double
quotes.
For more about specifying packages, see 'go help packages'.
For more about where packages and binaries are installed,
run 'go help gopath'. For more about calling between Go and C/C++,
run 'go help c'.
See also: go install, go get, go clean.
Makefile:30: recipe for target 'runc' failed
make: *** [runc] Error 2
Best,
Ekin
--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/