On Mon, Jan 7, 2019 at 1:33 AM Jan Mercl <0xj...@gmail.com> wrote:
>
> On Wed, Dec 19, 2018 at 1:27 AM Filippo Valsorda wrote:
> >
> > We have just released go1.12beta1, a beta version of Go 1.12.
> > It is cut from the master branch at the revision tagged go1.12beta1.
> ...
> > Report any
On Wed, Dec 19, 2018 at 1:27 AM Filippo Valsorda wrote:
>
> We have just released go1.12beta1, a beta version of Go 1.12.
> It is cut from the master branch at the revision tagged go1.12beta1.
...
> Report any problems using the issue tracker:
> https://golang.org/issue/new
Sorry, I cannot use
On Thu, Dec 20, 2018 at 2:32 PM Peter Kleiweg wrote:
>
> Ian Lance Taylor schreef op 20 december 2018 23:10:17 CET:
> > On Thu, Dec 20, 2018 at 10:58 AM Peter Kleiweg
> > wrote:
> > >
> > > Ian Lance Taylor schreef op 20 december 2018
> > 19:20:13 CET:
> > > > Adding the file with the local
Ian Lance Taylor schreef op 20 december 2018 23:10:17 CET:
> On Thu, Dec 20, 2018 at 10:58 AM Peter Kleiweg
> wrote:
> >
> > Ian Lance Taylor schreef op 20 december 2018
> 19:20:13 CET:
> > > Adding the file with the local configuration should work just as
> well
> > > when you need to adjust
On Thu, Dec 20, 2018 at 10:58 AM Peter Kleiweg wrote:
>
> Ian Lance Taylor schreef op 20 december 2018 19:20:13 CET:
> > On Thu, Dec 20, 2018 at 8:02 AM Peter Kleiweg
> > wrote:
> > >
> > > Ian Lance Taylor schreef op 20 december 2018
> > 16:47:20 CET:
> > > > On Thu, Dec 20, 2018 at 1:07 AM
On Thu, 20 Dec 2018 19:58:15 +0100
Peter Kleiweg wrote:
> I don't need make. A simple script will do.
> Or rather, it should. I can install the packages,
> but I can't import them because Go is too limited
> to remember the necessary environment settings.
You said you use a wrapper script
Ian Lance Taylor schreef op 20 december 2018 19:20:13 CET:
> On Thu, Dec 20, 2018 at 8:02 AM Peter Kleiweg
> wrote:
> >
> > Ian Lance Taylor schreef op 20 december 2018
> 16:47:20 CET:
> > > On Thu, Dec 20, 2018 at 1:07 AM Peter Kleiweg
> > > wrote:
> > > >
> > > > Ian Lance Taylor schreef op
On Thu, Dec 20, 2018 at 8:02 AM Peter Kleiweg wrote:
>
> Ian Lance Taylor schreef op 20 december 2018 16:47:20 CET:
> > On Thu, Dec 20, 2018 at 1:07 AM Peter Kleiweg
> > wrote:
> > >
> > > Ian Lance Taylor schreef op 20 december 2018
> > 00:06:58 CET:
> > >
> > > > How about this:
> > > >
> >
Ian Lance Taylor schreef op 20 december 2018 16:47:20 CET:
> On Thu, Dec 20, 2018 at 1:07 AM Peter Kleiweg
> wrote:
> >
> > Ian Lance Taylor schreef op 20 december 2018
> 00:06:58 CET:
> >
> > > How about this:
> > >
> > > Move the C files to a subdirectory. Write a script or Makefile
> that
>
On Thu, Dec 20, 2018 at 1:07 AM Peter Kleiweg wrote:
>
> Ian Lance Taylor schreef op 20 december 2018 00:06:58 CET:
>
> > How about this:
> >
> > Move the C files to a subdirectory. Write a script or Makefile that
> > compiles the C files into a .syso file in the main package directory,
> >
Ian Lance Taylor schreef op 20 december 2018 00:06:58 CET:
> How about this:
>
> Move the C files to a subdirectory. Write a script or Makefile that
> compiles the C files into a .syso file in the main package directory,
> using flags that you specify. Fetch the package using `go get -d`.
>
On Wed, Dec 19, 2018 at 2:55 PM Peter Kleiweg wrote:
>
> Ian Lance Taylor schreef op 19 december 2018 23:27:13 CET:
> > On Wed, Dec 19, 2018 at 2:15 PM Peter Kleiweg
> > wrote:
> > >
> > > > I assume that the recompile fails because compiling the C code
> > fails.
> > > You should compile the C
Ian Lance Taylor schreef op 19 december 2018 23:27:13 CET:
> On Wed, Dec 19, 2018 at 2:15 PM Peter Kleiweg
> wrote:
> >
> > > I assume that the recompile fails because compiling the C code
> fails.
> > You should compile the C code yourself, producing a .syso file. You
> > should add that .syso
On Wed, Dec 19, 2018 at 2:15 PM Peter Kleiweg wrote:
>
> > I assume that the recompile fails because compiling the C code fails.
> You should compile the C code yourself, producing a .syso file. You
> should add that .syso file to your package directory. You should
> remove the C code from your
> I assume that the recompile fails because compiling the C code fails.
You should compile the C code yourself, producing a .syso file. You
should add that .syso file to your package directory. You should
remove the C code from your package directory--you can still put it in
a subdirectory, of
On Wed, Dec 19, 2018 at 10:50 AM Peter Kleiweg wrote:
>
> How do I do what runtime/race does? Is it what I want?
>
> I have a package with C and Go files. I want to install that package. Then I
> want to import that package into a program, and build that program without
> recompiling the
How do I do what runtime/race does? Is it what I want?
I have a package with C and Go files. I want to install that package. Then I
want to import that package into a program, and build that program without
recompiling the package. Because recompile fails.
How do I do that? This was an issue
On Tue, Dec 18, 2018 at 10:07 PM Peter Kleiweg wrote:
>
> Go 1.12 is the last release that will support binary-only packages.
>
> What are the alternatives?
>
> I need binary-only packages for packages that use cgo with non-standard
> environment variable values.
You can compile your C code
Go 1.12 is the last release that will support binary-only packages.
What are the alternatives?
I need binary-only packages for packages that use cgo with non-standard
environment variable values.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
Hello gophers,
We have just released go1.12beta1, a beta version of Go 1.12.
It is cut from the master branch at the revision tagged go1.12beta1.
Please try your production load tests and unit tests with the new version.
Your help testing these pre-release versions is invaluable.
Report any
20 matches
Mail list logo
