On Fri, Jul 17, 2015 at 3:47 PM, strongq wrote:
> Now I’m running into new problem. I’m trying to enable “--with-python
> option” for building gdb.
>
> For the native Linux version, I just need to install Python-dev package. But
> for cross compiling the windows version, I don’t know which Linux p
Now I’m running into new problem. I’m trying to enable “--with-python option”
for building gdb.
For the native Linux version, I just need to install Python-dev package. But
for cross compiling the windows version, I don’t know which Linux package is
for mingw. It cannot find the ‘Python.h’.
increase the timeout setting bigger than 10 seconds.
Thanks,
Qyq
From: Victor Chong [mailto:victor.ch...@linaro.org]
Sent: Friday, July 17, 2015 12:20 PM
To: strongq
Cc: Rob Savoye; Jim Wilson; Linaro Toolchain Mailman List
Subject: Re: abe: cross native toolchain compilation for aarch64-linux
You can try the --timeout option to abe.sh to increase the timeout value
for wget.
Or add "wget_timeout=" to ~/.aberc if you don't want to type it
every time.
On Sat, Jul 18, 2015 at 1:04 AM, strongq wrote:
> Hi Rob, Jim,
>
> I'm frequently getting timeout for wget to fetch snapshot. Shouldn't t
Hi Rob, Jim,
I'm frequently getting timeout for wget to fetch snapshot. Shouldn't the
timeout setting in abe.sh use gt but not lt as below:
--time*|-time*)
check_directive $1 timeout "time" $2
if test $2 -lt 11; then
wget_timeout=$2
else
olchain Mailman List'
Subject: Re: abe: cross native toolchain compilation for aarch64-linux-gnu
On 07/16/2015 04:30 PM, strongq wrote:
> Also, I did sync to master branch of ABE, because the 'stable' branch
> does not support " --with-fileserver=148.251.136.42
> -
On 07/16/2015 04:30 PM, strongq wrote:
> Also, I did sync to master branch of ABE, because the 'stable' branch does
> not support " --with-fileserver=148.251.136.42
> --with-remote-snapshots=/snapshots-ref
> " options for configure.
'stable' is used more for validation, so doesn't change as of
: Thursday, July 16, 2015 6:30 PM
To: 'Jim Wilson'
Cc: 'Linaro Toolchain Mailman List'
Subject: RE: abe: cross native toolchain compilation for aarch64-linux-gnu
Thanks, Jim. Now I'm clear why it does not need three steps that I originally
thought it should be.
I'm buildin
lto:jim.wil...@linaro.org]
Sent: Thursday, July 16, 2015 4:32 PM
To: strongq
Cc: Linaro Toolchain Mailman List
Subject: Re: abe: cross native toolchain compilation for aarch64-linux-gnu
On Thu, Jul 16, 2015 at 12:40 PM, strongq wrote:
> The config.log is under
> "_build/builds/i6
On 07/16/2015 02:31 PM, Jim Wilson wrote:
> You could also try looking at
> http://crosstool-ng.org
> It is another set of scripts like abe to do builds.
In ABE, there is scripts/MakeRelease.job, which is what I use from
Jenkins to build Canadian cross binary releases.
- rob -
On Thu, Jul 16, 2015 at 12:40 PM, strongq wrote:
> The config.log is under
> "_build/builds/i686-w64-mingw32/aarch64-none-elf/binutils-gdb.git~linaro_binutils-2_24-branch-binutils/libiberty"
> My understanding that it is for building the binutils.
Yes. So I was looking at the wrong config.log f
t involved during the
build, isn't it?
Thanks,
Qyq
-Original Message-
From: Jim Wilson [mailto:jim.wil...@linaro.org]
Sent: Wednesday, July 15, 2015 4:14 PM
To: strongq
Cc: Linaro Toolchain Mailman List
Subject: Re: abe: cross native toolchain compilation for aarch64-linux-gnu
On 07/15/2015 02:13 PM, Jim Wilson wrote:
> This compiler is able to link, so we are able to do link tests here.
> GCC_NO_EXECUTABLES should not be set.
Is the cross compiler built successfully ? I usually only see this
error when there isn't a functioning C compiler, or somebody is trying
to bu
On Tue, Jul 14, 2015 at 8:10 PM, strongq wrote:
> Based on the last several line, since I'm doing cross compiling, $gcc_no_link
> should be set to yes. So I'm very confused about this. Frankly, I'm not very
> familiar with autoconf and those scripts. I just want some simple instruction
> to do
On Tue, Jul 14, 2015 at 8:10 PM, strongq wrote:
> Thanks Wilson for your reply. I was very busy and finally got some time on
> this.
> First, I followed your suggestion, built a 'Hello world' program with
> i686-w64-mingw32-gcc. The generated executable runs well on Windows PC.
>
> So I back to
abled which leads to problem for using it
with certain target. The previous 4.8.2014.9 release is less than 5M and it
works perfect.
Hopefully you and others can help me understand what I did wrong or missed.
Thank you,
Qyq
-Original Message-
From: Jim Wilson [mailto:jim.wil...@linaro.org]
On Fri, Jul 10, 2015 at 8:49 AM, strongq wrote:
> First build this: ../abe/abe.sh --target aarch64-none-elf –build all
> Then do 2nd round build: ../abe/abe.sh –host i686-w64-mingw32 --target
> aarch64-none-elf –build all
I just tried this on an Ubuntu 14.04 LTS system using the master
branch of
I'm trying to build the toolchain as win32 executable on Ubuntu with ABE.
I'm pretty new with ABE. I followed the FAQ
https://wiki.linaro.org/WorkingGroups/ToolChain/FAQ and Rob's post. Also
checked the MakeRelease.job and slave.sh. I have all packages listed in the
slave.sh installed. So I assume
On 06/03/2015 12:23 PM, Jim Wilson wrote:
> On Wed, Jun 3, 2015 at 9:26 AM, Virendra Kumar Pathak
> wrote:
>> I am trying to build a cross-native toolchain for AARCH64 using ABE build
>> framework.
>> By cross native I mean that toolchain will be build on 0x86 (Red hat
>> Santiago 6.4), it will ru
On Wed, Jun 3, 2015 at 9:26 AM, Virendra Kumar Pathak
wrote:
> I am trying to build a cross-native toolchain for AARCH64 using ABE build
> framework.
> By cross native I mean that toolchain will be build on 0x86 (Red hat
> Santiago 6.4), it will run on AARCH64 (Juno) and
> will produce binaries to
20 matches
Mail list logo