Signed-off-by: Adrian Dudau
---
meta-openstack/classes/identity.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-openstack/classes/identity.bbclass
b/meta-openstack/classes/identity.bbclass
index 672f6c4..3601f52 100644
--- a/meta-openstack/classes/identity.bbclas
A newer version of the recipe is maintained in meta-openembedded/meta-oe.
No reason to keep an older version here.
Signed-off-by: Adrian Dudau
---
.../multipath-tools/multipath-tools_git.bb | 46 --
1 file changed, 46 deletions(-)
delete mode 100644 recipes-extended/
On Mon, Sep 19, 2016 at 3:33 PM, Jason Wessel
wrote:
> The go-cross package is explicitly for compiling target libraries on
> the host system. When the target architecture matches the host
> architecture it will actually use the host's linker and compiler
> however which can result in the generat
The go-cross package is explicitly for compiling target libraries on
the host system. When the target architecture matches the host
architecture it will actually use the host's linker and compiler
however which can result in the generation of the cgo.a library having
linker symbols which might not
On 09/20/2016 09:57 AM, Mark Asselstine wrote:
On Mon, Sep 19, 2016 at 3:33 PM, Jason Wessel
wrote:
The go-cross package is explicitly for compiling target libraries on
the host system. When the target architecture matches the host
architecture it will actually use the host's linker and compil
On Tue, Sep 20, 2016 at 1:01 PM, Jason Wessel
wrote:
> The go-cross package is explicitly for compiling target libraries on
> the host system. When the target architecture matches the host
> architecture it will actually use the host's linker and compiler
> however which can result in the generat
