[gentoo-catalyst] [PATCH] add arm64 support

[gentoo-catalyst] [PATCH] add arm64 support

[Mike Frysinger]

---
 arch/arm64.py | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 arch/arm64.py

diff --git a/arch/arm64.py b/arch/arm64.py
new file mode 100644
index 0000000..f665e89
--- /dev/null
+++ b/arch/arm64.py
@@ -0,0 +1,16 @@
+
+import builder,os
+from catalyst_support import *
+
+class arch_arm64(builder.generic):
+	"builder class for arm64"
+	def __init__(self,myspec):
+		builder.generic.__init__(self,myspec)
+		self.settings["CHROOT"]="chroot"
+		self.settings["CFLAGS"]="-O2 -pipe"
+		self.settings["CFLAGS"]="-O2 -pipe"
+		self.settings["CHOST"]="aarch64-unknown-linux-gnu"
+
+def register():
+	"Inform main catalyst program of the contents of this plugin."
+	return ({ "arm64":arch_arm64 }, ("aarch64","arm64", ))
-- 
1.8.4.3

Re: [gentoo-catalyst] [PATCH] add arm64 support

[Rick "Zero_Chaos" Farina]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/21/2014 11:38 PM, Mike Frysinger wrote:
> ---
>  arch/arm64.py | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>  create mode 100644 arch/arm64.py
> 
> diff --git a/arch/arm64.py b/arch/arm64.py
> new file mode 100644
> index 0000000..f665e89
> --- /dev/null
> +++ b/arch/arm64.py
> @@ -0,0 +1,16 @@
> +
> +import builder,os
> +from catalyst_support import *
> +
> +class arch_arm64(builder.generic):
> +	"builder class for arm64"
> +	def __init__(self,myspec):
> +		builder.generic.__init__(self,myspec)
> +		self.settings["CHROOT"]="chroot"
> +		self.settings["CFLAGS"]="-O2 -pipe"
> +		self.settings["CFLAGS"]="-O2 -pipe"
> +		self.settings["CHOST"]="aarch64-unknown-linux-gnu"
> +
> +def register():
> +	"Inform main catalyst program of the contents of this plugin."
> +	return ({ "arm64":arch_arm64 }, ("aarch64","arm64", ))
> 

We are still working on a pretty major set of changes so I'll leave
dol-sen or someone else to commit but ACK, looks fine here.

- -Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJS3+hGAAoJEKXdFCfdEflK+O4QAJQdlMcizu0MP/HbuUvsv3A/
9K4qBBFAMJdjo2d+mKXvIANnGbZlKvLY2PtWD33ZUj5mpw5eHY4e886Z71RSY4zn
X2RvsKiBx9bUciUNqLfVXAP0deXxS4TzX03hyb/y5dIs4JD1z7erb7ov6eZWlbXc
znLHgzorvp9ZgIzRDA02kai8XEIaBeGdCoy8c2D/cdvvQFXJnvABEfvY4SOhwvf2
vR+JEme6zCkcsGU0SYu46uEb1434T6FfGPUuHH8M406gws+eavwLS5m56UO9rKX5
rVOv8H+IltEzJi0ctJMdiOLoEJmduorLIqKhFJOoUEQNQ4whWp07ARmM3vX446jC
Azo7T291tPHJIJXZiFNipn4gHW8FdR5TTgwoECSdIEdxstG/i3O3ix9OmjPYIUoX
ccQpBKqzoWYSrloW2l6wn7/EJW3SOuvkCMduh9jm/XjCnwuHtSNBFskUVw45wOuh
X53Rw+/dRUi9YcTgvSxvWdPTrKI8kQHBKPO8yVPMJg8O4efpJJqY0x4NcmY3mClu
rGV4h7AI0tP/2KGlzYI6iRpBgdbjtSw+Phz5JHjAjYW3ySZOLLsmKPpWaHUNkFgK
/5GgTBh6y+D8pQNUGdIHnYZQEJSMgUDx2cnafAe+8Gg/1YSq0u379CzCRAIPxvwp
4iqUEQN6vDXeN6ShLQ/N
=t/Qi
-----END PGP SIGNATURE-----

Re: [gentoo-catalyst] [PATCH] add arm64 support

[Brian Dolbec]

On Tue, 21 Jan 2014 23:38:43 -0500
Mike Frysinger <vapier@gentoo.org> wrote:

> ---
>  arch/arm64.py | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>  create mode 100644 arch/arm64.py
> 
> diff --git a/arch/arm64.py b/arch/arm64.py
> new file mode 100644
> index 0000000..f665e89
> --- /dev/null
> +++ b/arch/arm64.py
> @@ -0,0 +1,16 @@
> +
> +import builder,os
> +from catalyst_support import *
> +
> +class arch_arm64(builder.generic):
> +	"builder class for arm64"
> +	def __init__(self,myspec):
> +		builder.generic.__init__(self,myspec)
> +		self.settings["CHROOT"]="chroot"
> +		self.settings["CFLAGS"]="-O2 -pipe"
> +		self.settings["CFLAGS"]="-O2 -pipe"
> +		self.settings["CHOST"]="aarch64-unknown-linux-gnu"
> +
> +def register():
> +	"Inform main catalyst program of the contents of this plugin."
> +	return ({ "arm64":arch_arm64 }, ("aarch64","arm64", ))


I modified the patch to apply to the restructured paths in the pending
branch.  Since it should not affect the rewrite patches to be merged.
I've applied it to the pending branch which should be merged to master
soon.

Please checkout the pending branch and test run it please to ensure it
works the way you submitted (or better ;) )

The code can run from directly from the checkout.  There is even a
convenience file in the base directory called testpath.
Edit a catalyst.conf. (and  possibly a catalyst.rc) to use the checkout
directory files.

 from a terminal:

source ./testpath
catalyst -c my-local-test.conf -f some-stage.spec

You could also edit a copy of the catalyst-2.9999 ebuild to point
to the pending branch and install it.

P.S.  Be aware that the pending branch can/does get force pushes in
preparation for final merge into master.

-- 
Brian Dolbec <dolsen>