I am writing a spec file to build an app. The build failed with this error:
*** ERROR: No build ID note found in /home/makerpm/rpmbuild/BUILDROOT/mattermost-3.4-1.fc24.x86_64/usr/share/webapps/mattermost/bin/platform
Googling it, I found a few "tricks" which I tried but don't work: - Adding "LDFLAGS+=--build-id" - adding %global _missing_build_ids_terminate_build 0
What can I do to solve this issue ?
Note: the application is written in Go.
Thank you for help.
On Fri, Nov 4, 2016 at 9:19 AM arnaud gaboury arnaud.gaboury@gmail.com wrote:
I am writing a spec file to build an app. The build failed with this error:
*** ERROR: No build ID note found in /home/makerpm/rpmbuild/BUILDROOT/mattermost-3.4-1.fc24.x86_64/usr/share/webapps/mattermost/bin/platform
Googling it, I found a few "tricks" which I tried but don't work:
- Adding "LDFLAGS+=--build-id"
- adding %global _missing_build_ids_terminate_build 0
What can I do to solve this issue ?
Not sure it is a good idea, but adding this : %define debug_package %{nil}
removed the error and package builds fine. Is this a solution or a dirty trick to avoid ?
Note: the application is written in Go.
Thank you for help.
On 4 November 2016 at 08:34, arnaud gaboury arnaud.gaboury@gmail.com wrote:
On Fri, Nov 4, 2016 at 9:19 AM arnaud gaboury arnaud.gaboury@gmail.com wrote:
I am writing a spec file to build an app. The build failed with this error:
*** ERROR: No build ID note found in /home/makerpm/rpmbuild/BUILDROOT/mattermost-3.4-1.fc24.x86_64/usr/share/webapps/mattermost/bin/platform
Googling it, I found a few "tricks" which I tried but don't work:
- Adding "LDFLAGS+=--build-id"
- adding %global _missing_build_ids_terminate_build 0
What can I do to solve this issue ?
Not sure it is a good idea, but adding this : %define debug_package %{nil}
removed the error and package builds fine. Is this a solution or a dirty trick to avoid ?
Note: the application is written in Go.
Thank you for help.
Since it is writtenm in Go you'll probably find it helpful to read through and attempt to adhere to the draft Go guidelines: