On 8/8/19 7:56 PM, Matt Madison wrote:
On Wed, Aug 7, 2019 at 10:36 PM Changqing Li <[email protected]> wrote:
On 8/7/19 10:16 PM, Richard Purdie wrote:
On Wed, 2019-08-07 at 10:35 +0800, Changqing Li wrote:
On 8/6/19 6:47 PM, Richard Purdie wrote:
On Tue, 2019-08-06 at 14:54 +0800, [email protected]
wrote:
From: Changqing Li <[email protected]>
fix below error:
file /usr/lib64/go/src/cmd/cgo/zdefaultcc.go conflicts between
attempted installs of go-dev-1.12.6-r0.core2_64 and go-runtime-
dev-
1.12.6-r0.core2_64
file /usr/lib64/go/src/cmd/go/internal/cfg/zdefaultcc.go
conflicts
between attempted installs of go-dev-1.12.6-r0.core2_64 and go-
runtime-dev-1.12.6-r0.core2_64
Signed-off-by: Changqing Li <[email protected]>
---
meta/recipes-devtools/go/go-runtime_1.12.bb | 6 ++++++
meta/recipes-devtools/go/go_1.12.bb | 7 +++++++
2 files changed, 13 insertions(+)
It seems odd that both of these packages should provide this,
perhaps
one version should just be deleted?
Cheers,
Richard
These 2 recipes don't have any DEPEND or RDEPEND relationship, so
they
are independent from the point of recipe.
Make one of dev packages empty seems not proper ?
Let me put this another way. What is the difference between these two
binaries? When should you use one, when should you use the other? Or
are they the same thing?
Cheers,
Richard
go is for building go compiler, and go-runtime only contains go
standard runtime library
There are 2 use caes:
1. on target, user only install go-runtime to provide libstd.so for
other go apps.
2. on target, user install both go and go-runtime
in my opinion, only in case2, install dev pkg is meaningful, so maybe
we can remove the conflict
part of files from go-runtime.
@Matt, you have do lots of work related these recipes, could you also
give your opinion? Thanks.
Well, those 'z'-prefixed files are ones that are generated during the
build of go to embed default flags for the 'go' and 'cgo' commands to
use when they have to call on the C compiler. They also happen to be
generated during the build of go-runtime because go normally doesn't
separate its toolchain and runtime builds, whereas we have to for the
cross build case. So filtering those files out of the go-runtime-dev
package and leaving them in the go-dev package would probably be OK.
It's something of an artificial distinction, though.
Regards,
-Matt
Thanks, I will remove these 2 files from go-runtime-dev packages,
and send a v2 patch.
--
BRs
Sandy(Li Changqing)
--
BRs
Sandy(Li Changqing)
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
