On 05/04/11 03:07, Diane Holt wrote:
Nope -- all those files came with the CodeSourcery 4.4.1
(arm-2009q3-67-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2) -- I
just don't know what CS built them from. (I suppose if I can't find out
how to build them myself I could try just snagging them from
OK. Note that these do come from GLIBC, so building GLIBC for your
target using your new cross compiler should basically give you what
you want. I wouldn't be surprised if there's a Scratchbox package
that already provides these though.
-- Michael
On Tue, Apr 5, 2011 at 2:07 PM, Diane Holt wro
Nope -- all those files came with the CodeSourcery 4.4.1
(arm-2009q3-67-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2) -- I just
don't know what CS built them from. (I suppose if I can't find out how to
build them myself I could try just snagging them from my 4.4.1 toolchain and
seeing if they w
On Sat, Apr 2, 2011 at 1:07 PM, Diane Holt wrote:
> The good news is, my build completed successfully, once I put those extra
> libs in /usr/lib and updated my PATH to include the bin in the work area.
>
> The bad news is, there are a number of utililties that this build doesn't
> produce, that my
The good news is, my build completed successfully, once I put those extra
libs in /usr/lib and updated my PATH to include the bin in the work area.
The bad news is, there are a number of utililties that this build doesn't
produce, that my CodeSourcery 4.4.1 has:
arm-none-linux-gnueabi/libc/sbin:
Hi Michael,
Thanks for hanging in there with me :)
I know now why those three libs didn't build -- their configure-target-*
target failed, because when it tried to compile a little test program, the
loader couldn't find libmpc. I did include the --with-mpc flag in the
GCCFLAGS in your Makefile, b
Hi Diane. Please send through your configure arguments and a log of
the output of configure. I suspect that these libraries are somehow
half disabled leading to a later build error.
-- Michael
On Wed, Mar 30, 2011 at 3:20 PM, Diane Holt wrote:
> On Tue, Mar 29, 2011 at 6:18 PM, Michael Hope
>
On Tue, Mar 29, 2011 at 6:18 PM, Michael Hope wrote:
> >> The build got pretty far, but eventually failed with:
> >>
> >> make[4]: Entering directory
> >> `/home/ubuntu/work/build/gcc/libiberty/testsuite'
> >> make[4]: Nothing to be done for `install'.
> >> make[4]: Leaving directory
> `/home/ubun
On Tue, Mar 29, 2011 at 4:31 PM, Diane Holt wrote:
> Thanks, Michael, that's the sort of thing I was hoping for. And it almost
> worked :)
A great thing about Debian/Ubuntu is 'apt-get build-dep'. On recent
systems at least you can run 'apt-get build-dep gcc-snapshot' and have
all of the build d
I'm using Dapper because that's got an old enough libc to build the Linaro
toolchain against so that it will work as a toolchain in Scratchbox. The one
that was built by you guys won't work, because the
/scratchbox/host_shared/lib/libc.so is too old (and there are no current
plans to update it).
I
On Mon, Mar 28, 2011, Diane Holt wrote:
> The Dapper desktop VMWare appliance I got from Ubuntu [...]
Thanks a lot for sharing your notes!
If it's a requirement that you use Ubuntu 6.06, I'd be curious to hear
why! It should mostly work, but I'm curious because we mostly target
the latest LT
Thanks, Michael, that's the sort of thing I was hoping for. And it almost
worked :)
The Dapper desktop VMWare appliance I got from Ubuntu didn't have these
needed packages: bison, curl, flex, and texinfo. So I needed to install
them.
Without curl, the downloads won't happen.
Without texinfo, mak
On Sun, Mar 27, 2011 at 12:00 PM, Diane Holt wrote:
> Sorry, I should have been more specific. Yes, a cross-compiler for ARM
> (we're building for cortex-a8, which is why we're interested in the neon
> optimizations). As I mentioned, I can't use the one that's available as a
> debian pkg built by
Dnia 2011-03-26, sob o godzinie 16:00 -0700, Diane Holt pisze:
> As I mentioned, I can't use the one that's available as a
> debian pkg built by Linaro, because I need to use the toolchain in
> Scratchbox, which has a rather old libc (in its host_shared/lib), and
> the
> Linaro one was built again
Sorry, I should have been more specific. Yes, a cross-compiler for ARM
(we're building for cortex-a8, which is why we're interested in the neon
optimizations). As I mentioned, I can't use the one that's available as a
debian pkg built by Linaro, because I need to use the toolchain in
Scratchbox, wh
On 25/03/11 21:48, Diane Holt wrote:
I hope you don't mind me sending you mail, but I'm a bit stuck...I've
been told I need the Linaro 4.5.2 toolchain because it has some "neon
optimizations" that the CS 4.5.1 doesn't have.
In general, you'd be better addressing these questions on the Linaro
T
16 matches
Mail list logo
