Linux From Scratch This Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
09-16-2006, 07:01 PM
|
#1
|
Member
Registered: Sep 2006
Posts: 122
Rep:
|
Need help with SPECFILE=` gcc -- print-file specs`
Hello
On page 56 of the LFS 6.0 book I have to ammend the GCC spec file.
On the first line there are some single quotes that I am not sure if it's the same as the forward quotes
It has a much steeper slant then the regular quote.
Are there any special characters that I should use that I
don't normallty have on my keyboard ?
The other thing is not clear is in which directory should I be when I execute the command.
Right now I am getting an error at the mv command because it's trying to move it to the /usr/lib/gcc/i486-pc-linux-gnu/3.4.1/specs
and it's saying it is unable to remove target : Read only file system.
|
|
|
09-16-2006, 11:22 PM
|
#2
|
Senior Member
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914
Rep:
|
Didn't we already have this same exact post answered here just a couple days ago?  Maybe it was somewhere else. They are tics and can be found above your TAB key. You used them in your subject header.....
When you have long/complex commands, it's best to just copy/paste the whole lot to make sure you get it right.
|
|
|
09-18-2006, 06:22 AM
|
#3
|
LQ Veteran
Registered: Sep 2003
Posts: 10,532
|
Hi,
@jong357: Yep, we've had this question before: chapter 5.7 concerns
@status1: jong357 is correct on 2 accounts:
1) You probably did not use backtics but normal quote's.
2) If at all possible copy-paste the (syntactical complicated) commands.
|
|
|
09-18-2006, 06:37 PM
|
#4
|
Member
Registered: Sep 2006
Posts: 122
Original Poster
Rep:
|
Hello,
If it's the symbol that is under the ~ then yes I used the backtick
It's on the bottom next to the alt key on my laptop.
For some reason in the book it's tilted a lot more than it looks
on the keyboard and typed out.
In the book it looks almost horizontal to maybe 15 degrees while on the keyboard and on the screen it looks like 45 degrees.
I thought that there was some trick to making that symbol
So then the problem is somewhere else
I will give it another try over the weekend.
Is there more than one spec file ?
I tried to edit it by hand but I did find any mention of /lib/ld-linux.so.2
I will give it another try over the weekend maybe I missed something on the first try.
|
|
|
09-19-2006, 02:26 AM
|
#5
|
LQ Veteran
Registered: Sep 2003
Posts: 10,532
|
Hi,
Love to help you, but I also see that a previous problem hasn't been solved yet. It's pointless to continue if you do not solve that problem first.
BTW: SPECFILE is not a file, but a variable that holds the content of the output of the gcc --print.....command.
|
|
|
09-23-2006, 02:02 PM
|
#6
|
Member
Registered: Sep 2006
Posts: 122
Original Poster
Rep:
|
Hello,
Well I ran it again and as I suspected and as you explained the earlier problem
did not have any effect on the current error which still exists.
Here is the exact error
mv: inter-device move failed 'tempspecfile' to '/usr/lib/gcc/i486-pc-linux-gnu/
3.4.1/specs' : unable to remove target Read-only file system
|
|
|
09-23-2006, 02:27 PM
|
#7
|
LQ Veteran
Registered: Sep 2003
Posts: 10,532
|
Hi,
You are not allowed writing to /usr/lib/gcc/i486-pc-linux-gnu/. I do wonder if that destination is correct.......
Did you run make -C ld install (first command chapter 5.9) from within the binutils-build directory?
And what is the output of echo $SPECFILE after you do the SPECFILE=`gcc --print-file specs` and sed 's@ /lib/ld-linux.so.2@ /tools/lib/ld-linux.so.2@g' $SPECFILE > tempspecfile steps.
|
|
|
09-23-2006, 03:15 PM
|
#8
|
Member
Registered: Sep 2006
Posts: 122
Original Poster
Rep:
|
Hello,
Yes I ran the make -C ld install but I am not getting anything for
echo $SPECFILE just a blank line
|
|
|
09-23-2006, 03:30 PM
|
#9
|
Member
Registered: Sep 2006
Posts: 122
Original Poster
Rep:
|
Hello,
Actually I realize that I had a typo in the first line
I missed the $ before the SPECFILE
so now I have an error on the first line
bash: =/usr/lib/gcc/i486-pc-linux-gnu/3.4.1/specs: no such file or directory
|
|
|
09-23-2006, 03:31 PM
|
#10
|
LQ Veteran
Registered: Sep 2003
Posts: 10,532
|
Hi,
Quote:
echo $SPECFILE just a blank line
|
That's not correct, it should print a dirstructure that points to a file. I.e:
Code:
$ SPECFILE=`gcc --print-file specs`
$ echo $SPECFILE
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/specs
What happens when you run the following command: gcc --print-file specs
PS: You cannot use /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/specs, this is version dependent and does not correspond with LFS 6.0.
|
|
|
09-23-2006, 03:43 PM
|
#11
|
Member
Registered: Sep 2006
Posts: 122
Original Poster
Rep:
|
Hello
After I run gcc --print-file specs I get
/usr/lib/gcc/i486-pc-linux-gnu/3.4.1/specs
Which I have but it's a read only file system so I don't see how I can change it unless I move it somewhere else
|
|
|
09-23-2006, 04:00 PM
|
#12
|
LQ Veteran
Registered: Sep 2003
Posts: 10,532
|
Hi,
I don't think that /usr/lib/gcc/i486-pc-linux-gnu/3.4.1/specs has the correct path part. It should say something like: /tools/usr/lib/gcc/i486-pc-linux-gnu/3.4.1/specs (guessing here, don't have a half installed lfs 6.0 around  ).
gcc should point to /tools/bin/cc, is that so?
If not: you probably forget to do the ln -s gcc /tools/bin/cc step in chapter 5.5
|
|
|
09-23-2006, 04:12 PM
|
#13
|
Member
Registered: Sep 2006
Posts: 122
Original Poster
Rep:
|
Hello,
I did not forget that command
I just ran ln -s gcc /tools/bin/cc again and I got
ln: /tools/bin/cc : file exists
|
|
|
09-23-2006, 04:26 PM
|
#14
|
LQ Veteran
Registered: Sep 2003
Posts: 10,532
|
Hi,
What does which gcc tell you?
|
|
|
09-23-2006, 04:30 PM
|
#15
|
Member
Registered: Sep 2006
Posts: 122
Original Poster
Rep:
|
Hello,
After running which gcc I get
/usr/bin/gcc
|
|
|
All times are GMT -5. The time now is 06:18 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|