All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6944] New: building toolchain for sh4 fails
Date: Mon,  3 Mar 2014 00:07:01 +0000 (UTC)	[thread overview]
Message-ID: <bug-6944-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=6944

           Summary: building toolchain for sh4 fails
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: gdalex at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Hello support,

I'm trying to build a toolchain for Renesas SH4.

The process fails at the end with the following log:

make[3]: Leaving directory
`/home/g/toolchain/output/build/host-gcc-final-4.7.3/build/gcc'
make[2]: Leaving directory
`/home/g/toolchain/output/build/host-gcc-final-4.7.3/build'
make[1]: Leaving directory
`/home/g/toolchain/output/build/host-gcc-final-4.7.3/build'
if [ ! -e /home/g/toolchain/output/host/usr/bin/sh4-buildroot-linux-gnu-cc ];
then ln -snf sh4-buildroot-linux-gnu-gcc
/home/g/toolchain/output/host/usr/bin/sh4-buildroot-linux-gnu-cc; fi
if [ ! -e /home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/bin/cc ];
then ln -snf gcc
/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/bin/cc; fi
(cd /home/g/toolchain/output/host/usr/bin; for i in sh4-buildroot-linux-gnu-*;
do ln -snf $i sh4-linux${i##sh4-buildroot-linux-gnu}; done)
cp -dpf
/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libgcc_s*
/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/sysroot/lib/
cp: cannot stat
?/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libgcc_s*?: No
such file or directory
make:
[/home/g/toolchain/output/build/host-gcc-final-4.7.3/.stamp_host_installed]
Error 1 (ignored)
cp -dpf
/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libgcc_s*
/home/g/toolchain/output/target/lib/
cp: cannot stat
?/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libgcc_s*?: No
such file or directory
make:
[/home/g/toolchain/output/build/host-gcc-final-4.7.3/.stamp_host_installed]
Error 1 (ignored)
mkdir -p /home/g/toolchain/output/target/usr/lib
for i in  libstdc++ libmudflapth ; do cp -dpf
/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/${i}.so*
/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/sysroot/usr/lib/ ; cp
-dpf /home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/${i}.a
/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/sysroot/usr/lib/ ; cp
-dpf /home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/${i}.so*
/home/g/toolchain/output/target/usr/lib/ ; done
cp: cannot stat
?/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libstdc++.so*?:
No such file or directory
cp: cannot stat
?/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libstdc++.a?:
No such file or directory
cp: cannot stat
?/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libstdc++.so*?:
No such file or directory
cp: cannot stat
?/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libmudflapth.so*?:
No such file or directory
cp: cannot stat
?/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libmudflapth.a?:
No such file or directory
cp: cannot stat
?/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*/libmudflapth.so*?:
No such file or directory
make: ***
[/home/g/toolchain/output/build/host-gcc-final-4.7.3/.stamp_host_installed]
Error 1
g at g-ThinkPad-X220:~/toolchain/buildroot$ 




I'm using the SHA 5970e883419a55f25ea900d776287ae6ea34b62e from the buildroot
git repo.

The build tries to copy everything that's under
/home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*

Under that, I have only one folder named !m4



ls -la /home/g/toolchain/output/host/usr/sh4-buildroot-linux-gnu/lib*
total 12
drwxr-xr-x 3 g g 4096 Mar  2 14:16 .
drwxr-xr-x 6 g g 4096 Mar  2 14:23 ..
drwxr-xr-x 2 g g 4096 Mar  2 18:56 !m4


I guess the ! sign confuses the copy command.

I started the build with this command:  make O=../output toolchain

Attached is my config file.

Am I doing something wrong?



Cheers
George

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2014-03-03  0:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03  0:07 bugzilla at busybox.net [this message]
2014-03-03  0:07 ` [Buildroot] [Bug 6944] building toolchain for sh4 fails bugzilla at busybox.net
2014-03-03  7:52 ` bugzilla at busybox.net
2014-03-04 13:01 ` bugzilla at busybox.net
2014-03-04 13:02 ` bugzilla at busybox.net
2014-03-04 19:57 ` bugzilla at busybox.net
2014-04-24 20:03 ` bugzilla at busybox.net
2014-04-26 21:55 ` bugzilla at busybox.net
2014-04-29  5:21 ` bugzilla at busybox.net
2014-05-02 17:22 ` bugzilla at busybox.net
2014-05-17  8:57 ` bugzilla at busybox.net
2014-09-09 17:01 ` bugzilla at busybox.net
2015-06-03  1:29 ` bugzilla 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=bug-6944-163@https.bugs.busybox.net/ \
    --to=bugzilla@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.