From: "Kokkonda, Sundeep" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] rust: Merge all rustc-source patches into rust-source.inc
Date: Wed, 18 Jan 2023 09:05:22 -0800 [thread overview]
Message-ID: <17348.1674061522006889046@lists.openembedded.org> (raw)
In-Reply-To: <CAO5Uq5TRYjO+pUmoMur4O_jwZYJT1xuYk1iHkpMXjU2nofXYzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]
Without 'binutils' the required linker 'x86_64-poky-linux-ld' will not be added to the image (getting error - cannot find 'ld').
And, 'g++' also a required package along with 'gcc'. When removed 'g++' some required libs are missing. See below error.
root@qemux86-64:~/hello# cargo run
Compiling hello v0.1.0 (/home/root/hello)
error: linking with `x86_64-poky-linux-gcc` failed: exit status: 1
|
= note: "x86_64-poky-linux-gcc" "/tmp/rustcZTUudY/symbols.o" "/home/root/hello/target/debug/deps/hello-366ba9a14b055dd9.1rbu6cyq0fbr2z03.rcgu.o" "/home/root/hello/target/debug/deps/hello-366ba9a1"
= note: /usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find Scrt1.o: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find crti.o: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find crtbeginS.o: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find -lgcc_s: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find -lutil: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find -lrt: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find -lpthread: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find -lm: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find -ldl: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find -lc: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find crtendS.o: No such file or directory
/usr/lib/gcc/x86_64-poky-linux/12.2.0/../../../../x86_64-poky-linux/bin/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
error: could not compile `hello` due to previous error
[-- Attachment #2: Type: text/html, Size: 3094 bytes --]
next prev parent reply other threads:[~2023-01-18 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 9:48 [OE-Core][PATCH v2] rust: Merge all rustc-source patches into rust-source.inc Alex Kiernan
2023-01-16 7:00 ` [PATCH " Kokkonda, Sundeep
2023-01-16 9:33 ` [OE-core] " Alex Kiernan
2023-01-16 12:17 ` Kokkonda, Sundeep
2023-01-17 0:22 ` [OE-core] " Randy MacLeod
2023-01-18 11:43 ` Kokkonda, Sundeep
2023-01-18 12:01 ` [OE-core] " Alex Kiernan
2023-01-18 12:09 ` Kokkonda, Sundeep
2023-01-18 14:15 ` [OE-core] " Alex Kiernan
2023-01-18 17:05 ` Kokkonda, Sundeep [this message]
2023-01-18 17:25 ` Alex Kiernan
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=17348.1674061522006889046@lists.openembedded.org \
--to=sundeep.kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.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: 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.