From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001448]: buildroot cannot build gcc due to wrong option passed to 'exec'
Date: Sat, 28 Jul 2007 05:22:37 -0700 [thread overview]
Message-ID: <e5f3c3d35a4466ea2ba557107c5bb27b@bugs.uclibc.org> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1448
======================================================================
Reported By: pavko
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1448
Category: Architecture Specific
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 07-28-2007 05:22 PDT
Last Modified: 07-28-2007 05:22 PDT
======================================================================
Summary: buildroot cannot build gcc due to wrong option
passed to 'exec'
Description:
probably key point is:
buildroot_svn/toolchain_build_i686/gcc-4.2.1-initial/./gcc/as: line 2:
exec: -Q: invalid option
tried with gcc-4.2.0 with the same result.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
07-28-07 05:22 pavko New Issue
07-28-07 05:22 pavko Status new => assigned
07-28-07 05:22 pavko Assigned To => buildroot
======================================================================
next reply other threads:[~2007-07-28 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 12:22 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-29 21:03 [Buildroot] [buildroot 0001448]: buildroot cannot build gcc due to wrong option passed to 'exec' bugs at busybox.net
2007-07-30 7:41 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=e5f3c3d35a4466ea2ba557107c5bb27b@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