From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001446]: Buildroot compilation is broken for SH4 architecture
Date: Thu, 26 Jul 2007 13:57:04 -0700 [thread overview]
Message-ID: <4b492ec03fd99fce420f746e00d276af@bugs.uclibc.org> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1446
======================================================================
Reported By: fgretief
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1446
Category: Architecture Specific
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
======================================================================
Date Submitted: 07-26-2007 13:57 PDT
Last Modified: 07-26-2007 13:57 PDT
======================================================================
Summary: Buildroot compilation is broken for SH4 architecture
Description:
I am unable to do a build for the SH4 architecture.
Steps to reproduce:
- do a clean checkout/update (rev 19264)
svn://uclibc.org/trunk/buildroot
- rm .config* (just to make sure)
- make menuconfig
Select superh and SH4 architecture
Select uClibc 0.9.29 (instead of the snapshot)
Select cramfs as the root fs
- make
...
/bin/sh
/home/fgretief/src/buildroot/toolchain_build_sh4/gcc-4.2.1/gcc/../move-if-change
tmp-macro_list macro_list
echo timestamp > s-macro_list
The directory that should contain system headers does not exist:
/home/fgretief/src/buildroot/toolchain_build_sh4/uClibc_dev//usr/include
make[2]: *** [stmp-fixinc] Error 1
make[2]: Leaving directory
`/home/fgretief/src/buildroot/toolchain_build_sh4/gcc-4.2.1-initial/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory
`/home/fgretief/src/buildroot/toolchain_build_sh4/gcc-4.2.1-initial'
make: ***
[/home/fgretief/src/buildroot/toolchain_build_sh4/gcc-4.2.1-initial/.compiled]
Error 2
Note:
The binutils were never build. It started immediately with GCC-4.2.1
Directory listing after build:
-------------------------------------------------------------
~/src/buildroot$ ls -l
total 72
-rw-rw-r-- 1 fgretief fgretief 19191 Jul 24 21:30 Config.in
-rw-rw-r-- 1 fgretief fgretief 12072 Jul 26 22:07 Makefile
drwxrwxr-x 3 fgretief fgretief 4096 Jul 26 22:13 binaries
drwxrwxr-x 3 fgretief fgretief 4096 Jul 26 22:13 build_sh4
drwxrwxr-x 2 fgretief fgretief 4096 Jul 25 22:50 dl
drwxrwxr-x 4 fgretief fgretief 4096 Jul 22 13:08 docs
drwxrwxr-x 212 fgretief fgretief 4096 Jul 24 21:30 package
drwxrwxr-x 4 fgretief fgretief 4096 Jul 22 13:07 project
drwxrwxr-x 3 fgretief fgretief 4096 Jul 26 22:13 project_build_sh4
drwxrwxr-x 20 fgretief fgretief 4096 Jul 22 13:07 target
drwxrwxr-x 14 fgretief fgretief 4096 Jul 22 13:07 toolchain
drwxrwxr-x 4 fgretief fgretief 4096 Jul 26 22:14 toolchain_build_sh4
~/src/buildroot$ ls -l build_sh4/
total 4
drwxrwxr-x 5 fgretief fgretief 4096 Jul 26 22:13 staging_dir
~/src/buildroot$ ls -l project_build_sh4/
total 4
drwxrwxr-x 3 fgretief fgretief 4096 Jul 26 22:13 uclibc
~/src/buildroot$ ls -l toolchain_build_sh4/
total 8
drwxrwxr-x 25 fgretief fgretief 4096 Jul 26 22:14 gcc-4.2.1
drwxrwxr-x 9 fgretief fgretief 4096 Jul 26 22:15 gcc-4.2.1-initial
-------------------------------------------------------------
It looks like the error indicates to the fact that the kernel headers
where
never compiled/copied to their correct place. Seems like a dependency is
missing for kernel-headers and binutils.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
07-26-07 13:57 fgretief New Issue
07-26-07 13:57 fgretief Status new => assigned
07-26-07 13:57 fgretief Assigned To => buildroot
======================================================================
next reply other threads:[~2007-07-26 20:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 20:57 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-27 0:22 [Buildroot] [buildroot 0001446]: Buildroot compilation is broken for SH4 architecture bugs at busybox.net
2007-07-27 16:18 bugs at busybox.net
2007-08-01 21:34 bugs at busybox.net
2007-08-20 23:12 bugs at busybox.net
2007-08-23 13:56 bugs at busybox.net
2007-08-25 20:06 bugs at busybox.net
2007-08-26 18:57 bugs at busybox.net
2007-08-26 20:31 bugs at busybox.net
2007-08-26 20:41 bugs at busybox.net
2007-08-26 21:02 bugs at busybox.net
2007-09-19 14:08 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=4b492ec03fd99fce420f746e00d276af@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