How to provide crt1.o and crti.o for LFS?
Clash Royale CLAN TAG#URR8PPP
up vote
4
down vote
favorite
I have tried to create a Linux distribution with the Linux From Scratch (LFS) website. Everything went good until step 5.7. Glibc-2.19, but when I tried:
$LFS_TGT-gcc dummy.c
I get:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/../../../../i686-lfs-linux-gnu/bin/ld: cannot find crt1.o: No such file or directory
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/../../../../i686-lfs-linux-gnu/bin/ld: cannot find crti.o: No such file or directory
So I googled it for a while, and I realize that Debian changed some directory, and I searched for those files and I found them in:
/usr/libx32/
I realize from those searches that it happen with trying to compile 64 bit in 32 bit structures, and I should create virtual link of theme in:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/
But when I did that I got:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/crt1.o: file not recognized: File format not recognized
In this step I really don't know what to do next. How can I fix it?
debian gcc lfs
migrated from askubuntu.com Sep 6 '14 at 12:27
This question came from our site for Ubuntu users and developers.
add a comment |Â
up vote
4
down vote
favorite
I have tried to create a Linux distribution with the Linux From Scratch (LFS) website. Everything went good until step 5.7. Glibc-2.19, but when I tried:
$LFS_TGT-gcc dummy.c
I get:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/../../../../i686-lfs-linux-gnu/bin/ld: cannot find crt1.o: No such file or directory
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/../../../../i686-lfs-linux-gnu/bin/ld: cannot find crti.o: No such file or directory
So I googled it for a while, and I realize that Debian changed some directory, and I searched for those files and I found them in:
/usr/libx32/
I realize from those searches that it happen with trying to compile 64 bit in 32 bit structures, and I should create virtual link of theme in:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/
But when I did that I got:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/crt1.o: file not recognized: File format not recognized
In this step I really don't know what to do next. How can I fix it?
debian gcc lfs
migrated from askubuntu.com Sep 6 '14 at 12:27
This question came from our site for Ubuntu users and developers.
If "I should create virtual link of theme" mean that you created a symlink to a x86_64 library where a i686 library is expected, then no, you should never do that.
â Leiaz
Sep 6 '14 at 14:02
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I have tried to create a Linux distribution with the Linux From Scratch (LFS) website. Everything went good until step 5.7. Glibc-2.19, but when I tried:
$LFS_TGT-gcc dummy.c
I get:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/../../../../i686-lfs-linux-gnu/bin/ld: cannot find crt1.o: No such file or directory
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/../../../../i686-lfs-linux-gnu/bin/ld: cannot find crti.o: No such file or directory
So I googled it for a while, and I realize that Debian changed some directory, and I searched for those files and I found them in:
/usr/libx32/
I realize from those searches that it happen with trying to compile 64 bit in 32 bit structures, and I should create virtual link of theme in:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/
But when I did that I got:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/crt1.o: file not recognized: File format not recognized
In this step I really don't know what to do next. How can I fix it?
debian gcc lfs
I have tried to create a Linux distribution with the Linux From Scratch (LFS) website. Everything went good until step 5.7. Glibc-2.19, but when I tried:
$LFS_TGT-gcc dummy.c
I get:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/../../../../i686-lfs-linux-gnu/bin/ld: cannot find crt1.o: No such file or directory
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/../../../../i686-lfs-linux-gnu/bin/ld: cannot find crti.o: No such file or directory
So I googled it for a while, and I realize that Debian changed some directory, and I searched for those files and I found them in:
/usr/libx32/
I realize from those searches that it happen with trying to compile 64 bit in 32 bit structures, and I should create virtual link of theme in:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/
But when I did that I got:
/tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/crt1.o: file not recognized: File format not recognized
In this step I really don't know what to do next. How can I fix it?
debian gcc lfs
debian gcc lfs
edited Sep 6 '14 at 21:45
Peter Mortensen
79748
79748
asked Sep 6 '14 at 12:21
zokit
8618
8618
migrated from askubuntu.com Sep 6 '14 at 12:27
This question came from our site for Ubuntu users and developers.
migrated from askubuntu.com Sep 6 '14 at 12:27
This question came from our site for Ubuntu users and developers.
If "I should create virtual link of theme" mean that you created a symlink to a x86_64 library where a i686 library is expected, then no, you should never do that.
â Leiaz
Sep 6 '14 at 14:02
add a comment |Â
If "I should create virtual link of theme" mean that you created a symlink to a x86_64 library where a i686 library is expected, then no, you should never do that.
â Leiaz
Sep 6 '14 at 14:02
If "I should create virtual link of theme" mean that you created a symlink to a x86_64 library where a i686 library is expected, then no, you should never do that.
â Leiaz
Sep 6 '14 at 14:02
If "I should create virtual link of theme" mean that you created a symlink to a x86_64 library where a i686 library is expected, then no, you should never do that.
â Leiaz
Sep 6 '14 at 14:02
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
6
down vote
accepted
The correct virtual link is:
ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/
1
Nothing wrong with answering your own question! On the contrary, taking the time to share what you find is welcomed, appreciated and actively encouraged! It would be great if you could come back tomorrow (you have to wait a few hours, I forget how many, before accepting your own answer) and accept this as the correct answer too.
â terdonâ¦
Sep 6 '14 at 14:13
add a comment |Â
up vote
1
down vote
It should be noted that the the command below resolves the same issue on Fedora 28 as well.
`ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/`
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
accepted
The correct virtual link is:
ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/
1
Nothing wrong with answering your own question! On the contrary, taking the time to share what you find is welcomed, appreciated and actively encouraged! It would be great if you could come back tomorrow (you have to wait a few hours, I forget how many, before accepting your own answer) and accept this as the correct answer too.
â terdonâ¦
Sep 6 '14 at 14:13
add a comment |Â
up vote
6
down vote
accepted
The correct virtual link is:
ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/
1
Nothing wrong with answering your own question! On the contrary, taking the time to share what you find is welcomed, appreciated and actively encouraged! It would be great if you could come back tomorrow (you have to wait a few hours, I forget how many, before accepting your own answer) and accept this as the correct answer too.
â terdonâ¦
Sep 6 '14 at 14:13
add a comment |Â
up vote
6
down vote
accepted
up vote
6
down vote
accepted
The correct virtual link is:
ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/
The correct virtual link is:
ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/
edited Sep 6 '14 at 21:37
Peter Mortensen
79748
79748
answered Sep 6 '14 at 14:02
zokit
8618
8618
1
Nothing wrong with answering your own question! On the contrary, taking the time to share what you find is welcomed, appreciated and actively encouraged! It would be great if you could come back tomorrow (you have to wait a few hours, I forget how many, before accepting your own answer) and accept this as the correct answer too.
â terdonâ¦
Sep 6 '14 at 14:13
add a comment |Â
1
Nothing wrong with answering your own question! On the contrary, taking the time to share what you find is welcomed, appreciated and actively encouraged! It would be great if you could come back tomorrow (you have to wait a few hours, I forget how many, before accepting your own answer) and accept this as the correct answer too.
â terdonâ¦
Sep 6 '14 at 14:13
1
1
Nothing wrong with answering your own question! On the contrary, taking the time to share what you find is welcomed, appreciated and actively encouraged! It would be great if you could come back tomorrow (you have to wait a few hours, I forget how many, before accepting your own answer) and accept this as the correct answer too.
â terdonâ¦
Sep 6 '14 at 14:13
Nothing wrong with answering your own question! On the contrary, taking the time to share what you find is welcomed, appreciated and actively encouraged! It would be great if you could come back tomorrow (you have to wait a few hours, I forget how many, before accepting your own answer) and accept this as the correct answer too.
â terdonâ¦
Sep 6 '14 at 14:13
add a comment |Â
up vote
1
down vote
It should be noted that the the command below resolves the same issue on Fedora 28 as well.
`ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/`
add a comment |Â
up vote
1
down vote
It should be noted that the the command below resolves the same issue on Fedora 28 as well.
`ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/`
add a comment |Â
up vote
1
down vote
up vote
1
down vote
It should be noted that the the command below resolves the same issue on Fedora 28 as well.
`ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/`
It should be noted that the the command below resolves the same issue on Fedora 28 as well.
`ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/`
edited Sep 19 at 22:21
Goro
6,16552763
6,16552763
answered Sep 19 at 21:54
Brett Holman
485
485
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f154083%2fhow-to-provide-crt1-o-and-crti-o-for-lfs%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
If "I should create virtual link of theme" mean that you created a symlink to a x86_64 library where a i686 library is expected, then no, you should never do that.
â Leiaz
Sep 6 '14 at 14:02