Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001507]: Build fails for ARM920T, c++ compiler/gcj build
Date: Sun, 23 Sep 2007 12:58:33 -0700	[thread overview]
Message-ID: <78437bbe8fa73ff2d8a4bab5873091bb@bugs.uclibc.org> (raw)


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1507 
====================================================================== 
Reported By:                APOLAUF
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1507
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             09-23-2007 09:56 PDT
Last Modified:              09-23-2007 12:58 PDT
====================================================================== 
Summary:                    Build fails for ARM920T, c++ compiler/gcj build
Description: 
When attempting to build toolchain for ARM920t, with "Build/install c++
compiler and libsdc++" option and "build/install java compiler and
libgcj", the following error shows up no matter what distro I use (Fedora,
Debian, Gentoo, etc.):


)
# Now for the ugly 3.3.x soft float hack... 
#
#
# Ok... that's enough of that. ft
mkdir -p /root/buildroot/project_build_arm/uclibc/root/usr/lib
/root/buildroot/pro ject_build_arm/uclibc/root/usr/sbin
touch /root/buildroot/toolchain_build_arm/gcc-4.2.1-final/.installed 
# These are in /lib, so ...
rm -rf /root/bui
Idroot/project_build_arm/uclibc/root/usr/lib/libgcc_s*.so* 
cp -dpf
/root/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/lib/libgcc_s*
\
/root/buildroot/project_build_arm/uclibc/root/lib/ 
cp -dpf
/root/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/lib/libstdc++
/root/buildroot/project_build_arm/uclibc/root/usr/lib/
cp : cannot stat
?/root/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/lib/l
ibstdc++.so*? : Mo such file or directory
make : ***
[/root/buildroot/toolchain_build_arm/gcc-4.2.1-final/.libs_installed]
Error 1

I must have Java support on my toolchain, and this failure to compile
makes things very frustrating.  I saw something similar on these boards,
with the response being ~"fix your headers.", and stating that Gentoo had
correct headers. I'm using Gentoo, and it's apparently not helping. Please
help. Thanks,
-Adrian
====================================================================== 

---------------------------------------------------------------------- 
 APOLAUF - 09-23-07 09:58  
---------------------------------------------------------------------- 
the "ft" after "#Ok... that's enough of that" is my OCR software
incorrectly identifying the # symbol. I'm running this in a VM, and didn't
feel like piping the output over, so there may be a recognition error or
two. I took care to correct the rest of the output. 

---------------------------------------------------------------------- 
 UlfSamuelsson - 09-23-07 11:39  
---------------------------------------------------------------------- 
I have seen the same thing for the AVR32 build.
I traced it back to "configure" not beeing able to link.
This was because "crt1.o" was not found, when linking.
That disabled creating the *.so files.

I find this strange, since there is no crt1.asm in gcc
except for the SH architecture.
Did not have time to investigate further. 

---------------------------------------------------------------------- 
 APOLAUF - 09-23-07 12:58  
---------------------------------------------------------------------- 
So what can I do to get this to compile? I need gcj support or a JVM to run
on my busybox build. And I don't have room to statically link GCJ with
glibc (47MB for a  hello world app). Is there any toolchain that I can use
to build gcj cross-compiling support with static linking against uClibc? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-23-07 09:56  APOLAUF        New Issue                                    
09-23-07 09:56  APOLAUF        Status                   new => assigned     
09-23-07 09:56  APOLAUF        Assigned To               => buildroot       
09-23-07 09:58  APOLAUF        Note Added: 0002766                          
09-23-07 11:39  UlfSamuelsson  Note Added: 0002767                          
09-23-07 12:58  APOLAUF        Note Added: 0002769                          
======================================================================

             reply	other threads:[~2007-09-23 19:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-23 19:58 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-25  0:53 [Buildroot] [buildroot 0001507]: Build fails for ARM920T, c++ compiler/gcj build bugs at busybox.net
2007-09-24 16:55 bugs at busybox.net
2007-09-24 14:21 bugs at busybox.net
2007-09-23 20:21 bugs at busybox.net
2007-09-23 18:39 bugs at busybox.net
2007-09-23 16:58 bugs at busybox.net
2007-09-23 16:56 bugs at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=78437bbe8fa73ff2d8a4bab5873091bb@bugs.uclibc.org \
    --to=bugs@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox