toolchain-buildroot: create a relocatable one

-----Original Message-----
From: Noam Camus [mailto:noamc at ezchip.com]
Sent: Sunday, June 08, 2014 3:45 PM
To: Noam Camus
Cc: Tal Zilcer
Subject: [PATCH 1/1] toolchain-buildroot: create a relocatable one

From: Tal Zilcer <[email protected]>

This adds ability so that pre built buildroot toolchain and GDB can be used by others in different computers without the need to build them again.

Note: the toolchain/GDB is still depended on native libraries.

Signed-off-by Tal Zilcer <[email protected]>

Signed-off-by Noam Camus <[email protected]>

---
 package/expat/expat.mk                  |    4 ++++
 package/gmp/gmp.mk                      |    4 ++++
 package/mpc/mpc.mk                      |    4 ++++
 package/mpfr/mpfr.mk                    |    4 ++++
 toolchain/toolchain-buildroot/Config.in |    8 ++++++++
 5 files changed, 24 insertions(+), 0 deletions(-)

package/expat/expat.mk index renamed from package/expat/expat.mk +0 -0

4c37ba2..c9af121 100644

package/expat/expat.mk +0 -0

@@ -13,5 +13,9 @@ EXPAT_DEPENDENCIES = host-pkgconf  EXPAT_LICENSE = MIT

EXPAT_LICENSE_FILES = COPYING

package/expat/expat.mk +4 -0

+ifeq ($(BR2_TOOLCHAIN_BUILDROOT_STATIC),y)
+HOST_EXPAT_CONF_OPT = --disable-shared
+endif
+
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))

package/gmp/gmp.mk index renamed from package/gmp/gmp.mk +0 -0

f71a210..12502da 100644

package/gmp/gmp.mk +4 -0

@@ -12,5 +12,9 @@ GMP_LICENSE = LGPLv3+
 GMP_LICENSE_FILES = COPYING.LESSERv3
 GMP_DEPENDENCIES = host-m4
 
+ifeq ($(BR2_TOOLCHAIN_BUILDROOT_STATIC),y)
+HOST_GMP_CONF_OPT = --disable-shared
+endif
+
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))

package/mpc/mpc.mk index renamed from package/mpc/mpc.mk +0 -0

81ee5f0..436e86a 100644

package/mpc/mpc.mk +0 -0

@@ -11,5 +11,9 @@ MPC_LICENSE_FILES = COPYING.LESSER  MPC_INSTALL_STAGING

= YES MPC_DEPENDENCIES = gmp mpfr

package/mpc/mpc.mk +4 -0

+ifeq ($(BR2_TOOLCHAIN_BUILDROOT_STATIC),y)
+HOST_MPC_CONF_OPT = --disable-shared
+endif
+
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))

package/mpfr/mpfr.mk index renamed from package/mpfr/mpfr.mk +0 -0

52d88fe..7093cf6 100644

package/mpfr/mpfr.mk +4 -0

@@ -13,5 +13,9 @@ MPFR_INSTALL_STAGING = YES  MPFR_DEPENDENCIES = gmp
 MPFR_MAKE_OPT = RANLIB=$(TARGET_RANLIB)
 
+ifeq ($(BR2_TOOLCHAIN_BUILDROOT_STATIC),y)
+HOST_MPFR_CONF_OPT = --disable-shared
+endif
+
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))

toolchain/toolchain-buildroot/Config.in +8 -1

index eef9f9c..a66f816 100644
@@ -18,6 +18,14 @@ config BR2_TOOLCHAIN_BUILDROOT_VENDOR
 
 	  If you're not sure, just leave the default "buildroot" value.
 
+config BR2_TOOLCHAIN_BUILDROOT_STATIC
+	bool "static toolchain"
+	help
+	  This option builds toolchain and gdb with static libraries
+	  of mpc,mpfr,gmp, and expat.
+	  It enable one to copy toolchain around to different directory
+	  and even to another machine. Now toolchain is relocatable, enjoy.
+
 source "package/linux-headers/Config.in.host"
 
 choice
--

1.7.1

Please review below patch

-----Original Message-----
From: Thomas Petazzoni [mailto:thomas.petazzoni at free-electrons.com]
Sent: Sunday, June 08, 2014 3:55 PM
To: Noam Camus
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] FW: [PATCH 1/1] toolchain-buildroot: create a relocatable one

Dear Noam Camus,

Quoted 1 line · Noam Camus

Please review below patch

Please send it properly with git send-email :-)

Thanks!

Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering http://free-electrons.com

I wish to contribute.
However my organization security rules are not allowing me to send directly with send-email outside our organization.

So I send-email to myself and only through outlook and exchange server I can forward the email to buildroot.

Isn't there a way to send a patch as file?

If your company IT department is unable to understand which tools the company engineers need to properly contribute to open-source communities, I'd say you should create a GMail account, and use that as the SMTP server to send your e-mail. I believe that's what a lot of people do when they have to work in hostile environments.

Quoted 5 lines

If your company IT department is unable to understand which tools the company engineers need to properly contribute to open-source communities, I'd say you should create a GMail account, and use that as the SMTP server to send your e-mail. I believe that's what a lot of people do when they have to work in hostile environments.

[Noam Camus] Do I need to subscribe again with my gmail account? Is adding to command line --smtp-server=smtp.gmail.com is enough? What about the user name in gmail?
Any working example somewhere under doc?

See the EXAMPLE section of the git-send-email(1) man page (online at
http://git-scm.com/docs/git-send-email).

Quoted 2 lines

See the EXAMPLE section of the git-send-email(1) man page (online at
http://git-scm.com/docs/git-send-email).

I followed EXAMPLE section but /usr/libexec/git-core/git-send-email always
complains:
Unable to initialize SMTP properly. Check config and use --smtp-debug. VALUES: server=smtp.gmail.com encryption=tls maildomain=xxx.ezchip.com Debug=0 port=587 at /usr/libexec/git-core/git-send-email line 1041.

This is Net::SMTP->new() that always returns NULL. I used CPAN to install latest Net::SMTP.

Any ideas?

Hi Noam,

Quoted 11 lines · Noam Camus

Quoted 2 lines

See the EXAMPLE section of the git-send-email(1) man page (online at
http://git-scm.com/docs/git-send-email).

I followed EXAMPLE section but /usr/libexec/git-core/git-send-email always
complains:
Unable to initialize SMTP properly. Check config and use --smtp-debug. VALUES: server=smtp.gmail.com encryption=tls maildomain=xxx.ezchip.com Debug=0 port=587 at /usr/libexec/git-core/git-send-email line 1041.

This is Net::SMTP->new() that always returns NULL. I used CPAN to install latest Net::SMTP.

Any ideas?

Your friendly corporate firewall might be blocking outgoing traffic to port
587. Try doing 'telnet smtp.gmail.com 587'. If you get timeout, this is most likely the reason. Your best options is to talk to your IT department to let you access to outgoing port 587. If that fails I can think of two workarounds:

1. Use an external server you can control from withing your corporate network (SSH would be best, though I guess your firewall blocks SSH as well)

2. Tunnel SMTP over HTTP somehow. This is quite ugly.

Others on this list may have better solutions for this frustrating problem.

If it's purely a proxy problem, then you can use socat to let smtp go through the tunnel.
Set up git to use localhost as smtp server, and a port of your choice, for example 10587, and set up a socat instance:

socat TCP4-LISTEN:$localport,reuseaddr,fork PROXY:$proxy:$remotehost:$remoteport,proxyport=$proxyport,resolve

where localport=10587, remotehost=smtp.gmail.com, remoteport=587, proxy=proxy.yourcompany.com proxyport=8080 (whatever is the right port for your proxy)

Same trick can be used to forward IRC through the proxy.

[Noam Camus] Do I need to subscribe again with my gmail account?

Is adding to command line --smtp-server=smtp.gmail.com is enough? What about the user name in gmail?
Any working example somewhere under doc?