Quote:
Originally posted by rvijay
This was very true. I installed Knoppix to my Hard Drive and this has the gcc compiler.
However, I am having other problems.
lfs@ttyp0[binutils-build]$ { ./configure ... && ... && ... && make install; }
bash: ./configure: No such file or directory
lfs@ttyp0[binutils-build]$ ../binutils-2.14/configure --prefix=/tools --disable-nls
bash: ../binutils-2.14/configure: No such file or directory
lfs@ttyp0[binutils-build]$ cd
lfs@ttyp0[~]$ cd /mnt/hdb5/lfs-packages/binutils-2.14
lfs@ttyp0[binutils-2.14]$ ../binutils-2.14/configure --prefix=/tools --disable-nls
../binutils-2.14/configure: line 422: ./config.log: Read-only file system
lfs@ttyp0[binutils-2.14]$ make configure-host
make: *** No rule to make target `configure-host'. Stop.
lfs@ttyp0[binutils-2.14]$ make LDFLAGS="-all-static"
make: *** No targets specified and no makefile found. Stop.
In my /etc/fstab. other than cdrom, there are no read only file systems. Also there is no file called config.log
I added user lfs to sudoers file. Also gave write permission to directory config in the ../binutils-2.14
Nothing seems to help to change the file from Read only. Please assist.
Vijay
|
I'm assuming this is the first pass.
As has been pointed out, the '{ ./configure ... && ... && ... && make install; }' is incorrect even as a copy and paste. That's simply an example of the fact that you're supposed to wrap the build sequence in braces to execute as a single command for the 'time' command to time. The reason you want to do that is to find out what your SBU is, just so the later packages' build time will let you know what you're in for. So you need to issue the literal command:
Code:
time { ../binutils-2.14/configure --prefix=/tools --disable-nls && \
make configure-host && \
make LDFLAGS="-all-static" && \
make install; }
You also should have set the $LFS variable for simplicity's sake. So, assuming /mnt/hdb5 was $LFS, you could 'cd $LFS'. However, that's probably not what it is, or should be. I'd figure you'd make a '/mnt/lfs' and mount /dev/hdb5 to that.
If binutils is version 2.14 and you unpacked that in /mnt/hdb5/linux-packages, then it's likely you created your binutils-build directory in the root - so the proper command might be '../linux-packages/binutils-$VER/configure' or something. And you shouldn't be configuring in the source directory, regardless.
I'm not sure how far you need to back up, but I'd at least keep my source tarball and *assuming this is the first shot at binutils*, rm -rf the binutils and binutils-build dir, and start that much over. The point is that you want to have an unpacked source and a build-dir (preferably right next to it) and then get into the build-dir and configure from there - so the command needs to find that file from where you are. You should not need sudo or any special perms - you're 'lfs' and the files are owned by you.
So, like I say:
Code:
tar xzf binutils-2.14
mkdir binutils-build
cd binutils-build
time { ../binutils-2.14/configure --prefix=/tools --disable-nls && \
make configure-host && \
make LDFLAGS="-all-static" && \
make install; }
(Normally, you're supposed to 'cd' into the source dir and issue commands but, in this case, it's stupid because you're just going to 'cd' back out again. So just make the build-dir and 'cd' into it directly.)
HTH