public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1002112] New: Bad Date: Fri, 11 Dec 2015 19:15:00 -0000 [thread overview] Message-ID: <bug-1002112-777@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002112 Bug ID: 1002112 Summary: Bad Product: eCos Version: unknown Target: All Architecture/Host_ Other OS: Status: UNCONFIRMED Severity: enhancement Priority: low Component: Other Assignee: unassigned@bugs.ecos.sourceware.org Reporter: jinkis007@gmail.com QA Contact: ecos-bugs@ecos.sourceware.org CC: ecos-bugs@ecos.sourceware.org Created attachment 2644 --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2644&action=edit error not understood Hello, I'm Ajinkya Shendre. I'm trying to install eCos on my ubuntu system. In the building the toolchain section, there's a command '/src/binutils-2.13.1/configure --target=TARGET \ --prefix=/gnutools -v 2>&1 | tee configure.out '. In this command we are accessing the path /src/binutils-2.13.1/configure and i'm getting an error as 'bash: /src/binutils-2.13.1/configure: No such file or directory'. I'm not able to detect why this problem is occuring, help will be appreciated. I'm attaching the screenshot as well. Thank You. -- You are receiving this mail because: You are the assignee for the bug.
next reply other threads:[~2015-12-11 19:15 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-11 19:15 bugzilla-daemon [this message] 2016-01-08 16:07 ` [Bug 1002112] Don't know how to build toolchain on Ubuntu bugzilla-daemon 2015-12-11 19:15 [Bug 1002112] New: Bad bugzilla-daemon
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-1002112-777@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@ecoscentric.com \ --cc=unassigned@bugs.ecos.sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).