[SOLVED] mkdir: permission denied during binutils make install

andrea_g90 · 10-20-2010, 11:00 AM

Is it normal that when I issue the command

Code:

rm -r "folder"

I have to push "y" "enter" for every file write-protected?? How can I do to say yes to all?? I've done 8600 times "y" "enter" to delete perl, I hurt my fingers

druuna · 10-20-2010, 11:19 AM

Hi,

There might be an alias in place that adds the -i option to rm.

If you want to force the rm use the -f flag: rm -rf "folder". Be aware that you will remove folder and all that is attached to it and you cannot un-delete it!!.

Hope this helps.

andrea_g90 · 11-02-2010, 08:57 AM

I'm again back with another question: in chapter 6.3 the book talks about the package management, but it doesn't say a word about when install it, so is it important that I install it before continuing or can I do it later (when?)??

druuna · 11-02-2010, 09:07 AM

Hi,

Chapter 6.3 talks about possible package management.

Quote:

Before you begin to wonder, NO—this section will not talk about nor recommend any particular package manager. What it provides is a roundup of the more popular techniques and how they work. The perfect package manager for you may be among these techniques or may be a combination of two or more of these techniques.

Out of the box LFS does not come with a package management system. There are some hints available (mentioned in chapter 6.3) and there are also some success stories right here on LQ (Check this sub-forum, especially: Build notes for LFS 6.6 with package users. . .).

When and how you implement a package management system all depends on which package management system you choose. Have a good look at the available hints and the link I provided before you decide to pick one.

Hope this helps.

andrea_g90 · 11-02-2010, 09:30 AM

Ok, so I'll go ahead with lfs and later I'll see what to do with the package manager that is certainly more difficult seen that for me is the first time... Thanks!!

andrea_g90 · 11-02-2010, 04:08 PM

In chapter 6.6 the book says :

Code:

To remove the “I have no name!” prompt, start a new shell. Since a full Glibc was installed in Chapter 5 and the /
etc/passwd and /etc/group files have been created, user name and group name resolution will now work:

	Code:
	exec /tools/bin/bash --login +h
Note the use of the +h directive. This tells bash not to use its internal path hashing. Without this directive, bash
would remember the paths to binaries it has executed. To ensure the use of the newly compiled binaries as soon as
they are installed, the +h directive will be used for the duration of this chapter.

and then it continues with normal dictation.. I don't understand if I have to give

Code:

exec /tools/bin/bash --login +h

in the lfs shell or in a new shell of the host, and then I have to continue with the others dictations

Code:

touch /var/run/utmp /var/log/{btmp,lastlog,wtmp}
chgrp -v utmp /var/run/utmp /var/log/lastlog
chmod -v 664 /var/run/utmp /var/log/lastlog

in the lfs shell or in the same shell of the host?? I'm really confused

crts · 11-02-2010, 04:48 PM

You do this in the chrooted environment, i.e. the "lfs-shell". You also issue those commands in the very same chrooted environment unless told otherwise. Read this again:
http://www.linuxfromscratch.org/lfs/...06/chroot.html

Pay attention to the Note at the bottom.

andrea_g90 · 11-03-2010, 10:28 AM

I've solved yesterday's problems and now arrives the others of today....
chapter 6.9.1 GlibC: the book say something about applying patch in order to prevent building with gcc4.5.1 and make 3.8.1
Here is my output:

Code:

root:/sources/packages/glibc-2.12.1# patch -Np1 -i ../../patch/glibc-2.12.1-gcc_fix-1.patch 
patch: **** Can't create file /tmp/poHelJJI : No such file or directory
root:/sources/packages/glibc-2.12.1# patch -Np1 -i ../../patch/glibc-2.12.1-gcc_fix-1.patch 
patch: **** Can't create file /tmp/po67ixmj : No such file or directory
root:/sources/packages/glibc-2.12.1# patch -Np1 -i ../../patch/glibc-2.12.1-makefile_fix-1.patch 
patch: **** Can't create file /tmp/poMR9f5T : No such file or directory
root:/sources/packages/glibc-2.12.1#

As you can see patches aren't in the same folder of packages but in their own folder in sources, near package's folder!

crts · 11-03-2010, 11:59 AM

Quote:

Originally Posted by andrea_g90

I've solved yesterday's problems and now arrives the others of today....
chapter 6.9.1 GlibC: the book say something about applying patch in order to prevent building with gcc4.5.1 and make 3.8.1
Here is my output:

Code:

root:/sources/packages/glibc-2.12.1# patch -Np1 -i ../../patch/glibc-2.12.1-gcc_fix-1.patch 
patch: **** Can't create file /tmp/poHelJJI : No such file or directory
root:/sources/packages/glibc-2.12.1# patch -Np1 -i ../../patch/glibc-2.12.1-gcc_fix-1.patch 
patch: **** Can't create file /tmp/po67ixmj : No such file or directory
root:/sources/packages/glibc-2.12.1# patch -Np1 -i ../../patch/glibc-2.12.1-makefile_fix-1.patch 
patch: **** Can't create file /tmp/poMR9f5T : No such file or directory
root:/sources/packages/glibc-2.12.1#

As you can see patches aren't in the same folder of packages but in their own folder in sources, near package's folder!

Do you have a /tmp directory? I.e. what is the output of
ls -l /

andrea_g90 · 11-03-2010, 12:02 PM

No, there isn't.. this is the output:

Code:

root:/sources/packages/glibc-2.12.1# ls -l /
total 76
drwxr-xr-x   2 root root  4096 Nov  2 19:49 bin
drwxr-xr-x   2 root root  4096 Nov  2 19:41 boot
drwxr-xr-x  19 root root  3940 Nov  3 14:40 dev
drwxr-xr-x   3 root root  4096 Nov  2 19:53 etc
drwxr-xr-x   4 root root  4096 Oct 16 18:17 home
drwxr-xr-x   2 root root  4096 Nov  2 19:41 lib
lrwxrwxrwx   1 root root     3 Nov  2 19:43 lib64 -> lib
drwx------   2 root root 16384 Oct 17 03:51 lost+found
drwxr-xr-x   4 root root  4096 Nov  2 19:41 media
drwxr-xr-x   2 root root  4096 Nov  2 19:41 mnt
drwxr-xr-x   2 root root  4096 Nov  2 19:41 opt
dr-xr-xr-x 183 root root     0 Nov  3 15:40 proc
drwxr-x---   2 root root  4096 Nov  2 22:10 root
drwxr-xr-x   2 root root  4096 Nov  2 19:41 sbin
drwxrwxrwt   4 1001 root  4096 Oct 20 01:47 sources
drwxr-xr-x   2 root root  4096 Nov  2 19:41 srv
drwxr-xr-x  13 root root     0 Nov  3 15:40 sys
drwxr-xr-x  13 root root  4096 Oct 20 14:27 tools
drwxr-xr-x   9 root root  4096 Nov  2 19:43 usr
drwxr-xr-x  11 root root  4096 Nov  2 19:43 var
root:/sources/packages/glibc-2.12.1#

crts · 11-03-2010, 12:06 PM

Well, there should be at this point. You missed something in a previous chapter. Probably this command
install -dv -m 1777 /tmp /var/tmp

andrea_g90 · 11-03-2010, 12:14 PM

Quote:

Originally Posted by crts

Well, there should be at this point. You missed something in a previous chapter. Probably this command
install -dv -m 1777 /tmp /var/tmp

you're right, I've skipped that pass.. Thanks, now is all ok!

andrea_g90 · 11-03-2010, 12:51 PM

I've ran the test suit of glibc but I don't understand if some of this errors are listed in the book as usual so here is the output:

Code:

root:/sources/packages/glibc-build# grep Error glibc-check-log
make[2]: [/sources/packages/glibc-build/posix/annexc.out] Error 1 (ignored)
make[2]: *** [/sources/packages/glibc-build/posix/tst-vfork3.out] Error 1
make[1]: *** [posix/tests] Error 2
make[2]: *** [/sources/packages/glibc-build/nptl/tst-rwlock6.out] Error 1
make[2]: *** [/sources/packages/glibc-build/nptl/tst-rwlock7.out] Error 1
make[2]: *** [/sources/packages/glibc-build/nptl/tst-rwlock9.out] Error 1
make[2]: *** [/sources/packages/glibc-build/nptl/tst-rwlock11.out] Error 1
make[2]: *** [/sources/packages/glibc-build/nptl/tst-rwlock12.out] Error 11
make[2]: *** [/sources/packages/glibc-build/nptl/tst-rwlock14.out] Error 1
make[1]: *** [nptl/tests] Error 2
make[2]: *** [/sources/packages/glibc-build/rt/tst-cpuclock2.out] Error 1
make[1]: *** [rt/tests] Error 2
make[2]: *** [/sources/packages/glibc-build/elf/tst-xmmymm.out] Error 1
make[1]: *** [elf/tests] Error 2
make: *** [check] Error 2
root:/sources/packages/glibc-build#

I'm not sure especially about "posix/test", "elf/test" and "check", are they normal???

andrea_g90 · 11-03-2010, 05:01 PM

I've solved with glibc! and everything goes right until gmp because I haven't understand an important thing. When I specify what kind(x86 or amd 64) of operating system am I going to build?

Code:

If you are building for 32-bit x86, but you have a CPU which is capable of running 64-bit code and you
have specified CFLAGS in the environment, the configure script will attempt to configure for 64-bits and
fail. Avoid this by invoking the configure command below with

	Code:
	ABI=32 ./configure ...

I want to build a genuine 64 bit O.S. so can I simply skip this command??

Code:

ABI=32 ./configure ...

andrea_g90 · 11-04-2010, 12:38 AM

chapter 6.34 Autoconf: testsuite 75 (AS_BOX) failed:

Code:

.
.
.
M4sh.

 73: LINENO                                          ok
 74: LINENO stack                                    ok
 75: AS_BOX                                          FAILED (m4sh.at:155)
 76: AS_BASENAME                                     ok
.
.
.
477: autoscan                                        ok

## ------------- ##
## Test results. ##
## ------------- ##[]

ERROR: 437 tests were run,
5 failed (4 expected failures).
40 tests were skipped.
## -------------------------- ##
## testsuite.log was created. ##
## -------------------------- ##

Please send `tests/testsuite.log' and all information you think might help:

   To: <bug-autoconf@gnu.org>
   Subject: [GNU Autoconf 2.67] testsuite: 75 failed

You may investigate any problem if you feel able to do so, in which
case the test suite provides a good starting point.  Its output may
be found below `tests/testsuite.dir'.

make[3]: *** [check-local] Error 1
make[3]: Leaving directory `/sources/packages/autoconf-2.67/tests'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/sources/packages/autoconf-2.67/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/sources/packages/autoconf-2.67'
make: *** [check] Error 2
root:/sources/packages/autoconf-2.67#

Is this a critical error??