-
-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error during garble build #215
Comments
Can you share the code you're trying to obfuscate, or if not a minimally reproducible example? Otherwise we can only guess what happened here. |
@lu4p sorry, I can't since it's not an open source code. It's a package with some helper code. Nothing special. No idea, why the error tells about undefined symbols. Usual |
Do you use |
Can you run again with |
Also please provide the ouput of |
go env
|
@lu4p garble does not recognize |
|
I got the flag order mixed up |
@lu4p here the output. I've replaced some sensitive paths by
|
@lu4p I think I can share the pkg code, where error occurs. file chan.go:
file flag.go
file map.go
file mqtt.go
|
Looks like a CGO error to me? I see clang throwing a linker error, are you using CGO at all or is Go just implicitly using CGO because you're compiling for ARM? I've never compiled Go code to ARM before so I have no experience in that |
@capnspacehook last info I provided was about amd64 build, not arm. |
I'm going to label this "needs info" for now, because it's not a clear bug that we can reproduce or fix. I think, in general, bug reports without a way to reproduce the error will be hard to fix. |
@mvdan I gave all info that was requested. |
Indeed. It's just hard to request information in pieces when we don't know what the bug is about.
Yes, which is why I've been thinking about bug templates recently. I've opened #219 to automate this process some more. |
@mvdan I sent full errors code (with only replaced paths to packages). May be garble does not provide enough error context? |
Right. Which is why there's also #218. |
@mvdan when errors description will be extended, I will try to run garble on my project to provide more info. |
The base image has been updated to the latest go 1.15 release, updates burrowers/garble#215
@metalrex100 can you please try again? Some major refactors have been merged in the past week. We don't automatically fill a bug template just yet, but if we're lucky maybe your bug happened to be caused by the same problems that the refactors fixed. |
@mvdan thanks for the update. I tried to build my app with garble latest version. And build finished successfully! (if it's important, build has been done with golang version: |
@mvdan I faced with linker flags usage problem:
|
The good news: garble works with |
@mvdan I will close current issue since initial bug has been resolved. For bug with linker args usage new issue will be opened. |
this is solved, check my comment below no matter what I do - the error persists tried this simple code
and ran the only flag that seems to work is -o |
for anyone looking for solution - put your flags before |
I'm trying to build my go app binary on MacOs, but build fails with error:
I tried to build it with
GOARCH=arm GOOS=linux
envs, but build failed with another error:path/to/package
is my package. Sorry, can't write it here)It is the same project as in this issue: #202
Error in #202 issue seems like fixed, but as you can see new one appeared.
I'm using currently lates revision: e014f48
The text was updated successfully, but these errors were encountered: