View previous topic :: View next topic |
Author |
Message |
nlieb n00b
Joined: 01 Mar 2013 Posts: 12
|
Posted: Sat Mar 02, 2013 11:45 pm Post subject: Can't emerge genkernel - dependency issues |
|
|
So I got through compilation of my very first linux kernel ok (I've run Ubuntu before, but you really don't see much of the cli, let alone the kernel, in ubuntu). After coppying the compiled kernel into its own directory in /boot and attempting to emerge genkernel so I can install and build an initramfs, I get the following error:
>>> Failed to emerge app-arch/cpio-2.11, Log File:
>>> '/var/tmp/portage/app-arch/cpio-2.11/temp/build.log'
* Messages for package app-arch/cpio-2.11:
* Error: app-arch/cpio-2.11 failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 93: Called src_configure
* environment, line 2012: Called econf '--enable-nls' '--bindir=/bin' '--with-rmt=/usr/sbin/rmt'
* phase-helpers, line 501: Called die
* The specific snipped of code:
* die "econf failed"
Then some stuff about posting the above.
I got a different dependency error for nvidia-drivers (which I now know I can't install because the kernel on the livecd isn't supported - ah, shucks!), this time for dev-python/python-exec-0.2
This is less urgent as I suspect this is happening because I haven't installed my kernel yet. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54209 Location: 56N 3W
|
Posted: Sat Mar 02, 2013 11:52 pm Post subject: |
|
|
nlieb,
Please use wgetpaste to post the /var/tmp/portage/app-arch/cpio-2.11/temp/build.log
That will show what went wrong. We know its in the configure phase, which is when the bild system checks for all the things it needs. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
nlieb n00b
Joined: 01 Mar 2013 Posts: 12
|
Posted: Sun Mar 03, 2013 1:36 am Post subject: |
|
|
NeddySeagoon wrote: | nlieb,
Please use wgetpaste to post the /var/tmp/portage/app-arch/cpio-2.11/temp/build.log
That will show what went wrong. We know its in the configure phase, which is when the bild system checks for all the things it needs. |
Sorry, went out to fill some meds. Here's the output:[/code]
Code: | [32;01m * [39;49;00mPackage: app-arch/cpio-2.11
[32;01m * [39;49;00mRepository: gentoo
[32;01m * [39;49;00mMaintainer: base-system@gentoo.org
[32;01m * [39;49;00mUSE: abi_x86_64 amd64 elibc_glibc kernel_linux multilib nls userland_GNU
[32;01m * [39;49;00mFEATURES: sandbox
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
>>> Unpacking source...
>>> Unpacking cpio-2.11.tar.bz2 to /var/tmp/portage/app-arch/cpio-2.11/work
>>> Source unpacked in /var/tmp/portage/app-arch/cpio-2.11/work
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
>>> Preparing source in /var/tmp/portage/app-arch/cpio-2.11/work/cpio-2.11 ...
[32;01m*[0m Applying cpio-2.11-stat.patch ...
[A[120C [34;01m[ [32;01mok[34;01m ][0m
[32;01m*[0m Applying cpio-2.11-no-gets.patch ...
[A[120C [34;01m[ [32;01mok[34;01m ][0m
>>> Source prepared.
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
>>> Configuring source in /var/tmp/portage/app-arch/cpio-2.11/work/cpio-2.11 ...
* econf: updating cpio-2.11/build-aux/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating cpio-2.11/build-aux/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --enable-nls --bindir=/bin --with-rmt=/usr/sbin/rmt
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name...
configure: error: in `/var/tmp/portage/app-arch/cpio-2.11/work/cpio-2.11':
configure: error: C compiler cannot create executables
See `config.log' for more details.
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-arch/cpio-2.11/work/cpio-2.11/config.log
[31;01m*[0m ERROR: app-arch/cpio-2.11 failed (configure phase):
[31;01m*[0m econf failed
[31;01m*[0m
[31;01m*[0m Call stack:
[31;01m*[0m ebuild.sh, line 93: Called src_configure
[31;01m*[0m environment, line 2012: Called econf '--enable-nls' '--bindir=/bin' '--with-rmt=/usr/sbin/rmt'
[31;01m*[0m phase-helpers.sh, line 501: Called die
[31;01m*[0m The specific snippet of code:
[31;01m*[0m die "econf failed"
[31;01m*[0m
[31;01m*[0m If you need support, post the output of `emerge --info '=app-arch/cpio-2.11'`,
[31;01m*[0m the complete build log and the output of `emerge -pqv '=app-arch/cpio-2.11'`.
[31;01m*[0m The complete build log is located at '/var/tmp/portage/app-arch/cpio-2.11/temp/build.log'.
[31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/app-arch/cpio-2.11/temp/environment'.
[31;01m*[0m Working directory: '/var/tmp/portage/app-arch/cpio-2.11/work/cpio-2.11'
[31;01m*[0m S: '/var/tmp/portage/app-arch/cpio-2.11/work/cpio-2.11'
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory |
First time I've ever used wgetpaste, btw - handy tool. |
|
Back to top |
|
|
BillWho Veteran
Joined: 03 Mar 2012 Posts: 1600 Location: US
|
Posted: Sun Mar 03, 2013 1:52 am Post subject: |
|
|
nlieb,
Code: | configure: error: C compiler cannot create executables |
Did you make any changes to your compiler flags in make.conf _________________ Good luck
Since installing gentoo, my life has become one long emerge |
|
Back to top |
|
|
nlieb n00b
Joined: 01 Mar 2013 Posts: 12
|
Posted: Sun Mar 03, 2013 2:38 am Post subject: |
|
|
BillWho wrote: | nlieb,
Code: | configure: error: C compiler cannot create executables |
Did you make any changes to your compiler flags in make.conf |
I did, but none of the modifications I made were all that radical. I did notice that there were two CFLAGS lines (I must have just added a CFLAGS line without seeing there was already a CFLAGS line in the file), but removing that and its accompanying CXXFLAGS line didn't change the error message. My CFLAGS line reads
Code: | CFLAGS="-march=opteron-sse3 -o2 -pipe -msse -msse2 -msse3 -mmmx -m3dnow" |
If anything in that looks like it shouldn't be there, please tell me... |
|
Back to top |
|
|
nlieb n00b
Joined: 01 Mar 2013 Posts: 12
|
Posted: Sun Mar 03, 2013 2:43 am Post subject: |
|
|
Although it is a good thing I went in there as I noticed that sse3 and 3dnow were not in the use flags. Didn't change anything, though. |
|
Back to top |
|
|
BillWho Veteran
Joined: 03 Mar 2012 Posts: 1600 Location: US
|
Posted: Sun Mar 03, 2013 3:16 am Post subject: |
|
|
nlieb,
Check your output for -march=native
Code: | laptop bill # gcc -### -march=native -E /usr/include/stdlib.h 2>&1 | grep "/usr/libexec/gcc/.*cc1" |
My output is:
Code: | /usr/libexec/gcc/x86_64-pc-linux-gnu/4.6.3/cc1 -E -quiet /usr/include/stdlib.h "-march=corei7-avx" -mcx16 -msahf -mno-movbe -mno-aes -mpclmul -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-tbm -mavx -msse4.2 -msse4.1 --param "l1-cache-size=32" --param "l1-cache-line-size=64" --param "l2-cache-size=3072" "-mtune=corei7-avx"
|
It might be better than trying to figure out what to include. If in doubt change make.conf to CFLAGS="-O2 -march=native -pipe" and see if you can emerge cpio. _________________ Good luck
Since installing gentoo, my life has become one long emerge |
|
Back to top |
|
|
nlieb n00b
Joined: 01 Mar 2013 Posts: 12
|
Posted: Sun Mar 03, 2013 6:01 am Post subject: |
|
|
Tried changing the flags to what is listed under native, didn't work. Same with changing it to native. |
|
Back to top |
|
|
nlieb n00b
Joined: 01 Mar 2013 Posts: 12
|
Posted: Sun Mar 03, 2013 6:04 am Post subject: |
|
|
What about the use flags? |
|
Back to top |
|
|
BillWho Veteran
Joined: 03 Mar 2012 Posts: 1600 Location: US
|
Posted: Sun Mar 03, 2013 6:17 am Post subject: |
|
|
nlieb,
Paste back the output of:
Code: | n=$(users|awk '{print $1}');echo 'int main(){return 0;}' > /home/$n/dummy.c && gcc -v /home/$n/dummy.c -o /home/$n/dummy && rm /home/$n/dummy* |
_________________ Good luck
Since installing gentoo, my life has become one long emerge |
|
Back to top |
|
|
SamuliSuominen Retired Dev
Joined: 30 Sep 2005 Posts: 2133 Location: Finland
|
Posted: Sun Mar 03, 2013 7:51 am Post subject: |
|
|
nlieb wrote: |
Code: | CFLAGS="-march=opteron-sse3 -o2 -pipe -msse -msse2 -msse3 -mmmx -m3dnow" |
If anything in that looks like it shouldn't be there, please tell me... |
What is that -o2 doing there? -o is same as output, like `gcc 2.c -o 2` and you get a executable named 2 from source file 2.c |
|
Back to top |
|
|
BillWho Veteran
Joined: 03 Mar 2012 Posts: 1600 Location: US
|
Posted: Sun Mar 03, 2013 1:53 pm Post subject: |
|
|
nlieb wrote: | What about the use flags? |
Bad USE flag settings will cause problems other than not being able to compile.
paste back your make.conf _________________ Good luck
Since installing gentoo, my life has become one long emerge |
|
Back to top |
|
|
nlieb n00b
Joined: 01 Mar 2013 Posts: 12
|
Posted: Sun Mar 03, 2013 2:55 pm Post subject: |
|
|
ssuominen wrote: | nlieb wrote: |
Code: | CFLAGS="-march=opteron-sse3 -o2 -pipe -msse -msse2 -msse3 -mmmx -m3dnow" |
If anything in that looks like it shouldn't be there, please tell me... |
What is that -o2 doing there? -o is same as output, like `gcc 2.c -o 2` and you get a executable named 2 from source file 2.c |
Meant to put in -O2, fixed it. Still didn't solve the problem, though. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54209 Location: 56N 3W
|
Posted: Sun Mar 03, 2013 3:00 pm Post subject: |
|
|
nlieb,
With -o2, you couldn't emerge anything. With -O2 you should have got a different error.
Please pastebin the new build log. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
SamuliSuominen Retired Dev
Joined: 30 Sep 2005 Posts: 2133 Location: Finland
|
Posted: Tue Mar 05, 2013 5:14 am Post subject: |
|
|
When ./configure fails like that, it will leave a file config.log in the same directory as where the ./configure script is, as in somewhere in /var/tmp/portage/category_name/package_name/work/
So lets just PLEASE stop guessing and provide up-to-date config.log here so we can all stop guessing.
Thanks. |
|
Back to top |
|
|
|