[gentoo-user] emerge -e errors right after install

[gentoo-user] emerge -e errors right after install

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]

Hello, all.

Gentoo is absolutely great.

This is mainly to make clear I am pretty satisfied on how things are made
to let us have a Linux distro that does not use binary packages, everything
being built almost from the ground up.

But (here comes the "but"), right on the point I was able to build the
kernel (I'm using the live CD  from 08/01/2013 for x86_64 machine, and a
stage 3 tarballl from the same date for the same machine), I tried an
"emerge -e world", and there were so many errors that very few packages
were able to be completely built.

Mainly the errors are at the end of the "config" stage, and they are like:

...
config.status: creating Makefile
./config.status: line 1091: 26891 Done(141)               eval sed
\"\$ac_sed_extra\" "$ac_file_inputs"
     26892 Illegal instruction     | $AWK -f "$ac_tmp/subs.awk" >
$ac_tmp/out
config.status: error: could not create Makefile
...


or


...
configure: creating ./config.status
config.status: creating install-info/tests/defs
./config.status: line 1218: 31166 Done(141)               eval sed
\"\$ac_sed_extra\" "$ac_file_inputs"
     31167 Illegal instruction     | $AWK -f "$tmp/subs.awk" > $tmp/out
config.status: error: could not create install-info/tests/defs
...

or, like "xz-utils", that complained that it was unable to create a
Doxyfile, even having a

I have built binary packages for "sed" and "gawk", created in a machine
with the same characteristics and configuration, and emerged those to the
new machine.  Even so, the errors keep coming.

Am I too anxious?  I did not see anything further in the documentation that
could help this situation, so even not having finished all the installation
procedure, I think it should be possible, at this moment, right before
building a kernel (but after a few pages, right before section "9.
Installing Necessary System Tools").

In fact, it seems like there is one (or some) package(s) missing.

Thanks
Francisco

[-- Attachment #2: Type: text/html, Size: 2453 bytes --]

[gentoo-user] Re: emerge -e errors right after install

[Michael Palimaka]

On 16/08/2013 23:22, Francisco Ares wrote:
>       26892 Illegal instruction     | $AWK -f "$ac_tmp/subs.awk" >
>       31167 Illegal instruction     | $AWK -f "$tmp/subs.awk" > $tmp/out
 > [...]
> I have built binary packages for "sed" and "gawk", created in a machine
> with the same characteristics and configuration, and emerged those to
> the new machine.  Even so, the errors keep coming.

It could be an issue with faulty memory, or problem with glibc.

Often though, illegal instruction is the result of a mismatch between 
the host, and the target for which the binary was compiled.
This could be checked by comparing /proc/cpuinfo with your CFLAGs.

Re: [gentoo-user] Re: emerge -e errors right after install

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 781 bytes --]

2013/8/16 Michael Palimaka <kensington@gentoo.org>

> On 16/08/2013 23:22, Francisco Ares wrote:
>
>>       26892 Illegal instruction     | $AWK -f "$ac_tmp/subs.awk" >
>>       31167 Illegal instruction     | $AWK -f "$tmp/subs.awk" > $tmp/out
>>
> > [...]
>
>  I have built binary packages for "sed" and "gawk", created in a machine
>> with the same characteristics and configuration, and emerged those to
>> the new machine.  Even so, the errors keep coming.
>>
>
> It could be an issue with faulty memory, or problem with glibc.
>
> Often though, illegal instruction is the result of a mismatch between the
> host, and the target for which the binary was compiled.
> This could be checked by comparing /proc/cpuinfo with your CFLAGs.
>
>
>
Thanks, gonna check that.

Francisco

[-- Attachment #2: Type: text/html, Size: 1567 bytes --]

Re: [gentoo-user] Re: emerge -e errors right after install

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

2013/8/16 Francisco Ares <frares@gmail.com>

>
> 2013/8/16 Michael Palimaka <kensington@gentoo.org>
>
>> On 16/08/2013 23:22, Francisco Ares wrote:
>>
>>>       26892 Illegal instruction     | $AWK -f "$ac_tmp/subs.awk" >
>>>       31167 Illegal instruction     | $AWK -f "$tmp/subs.awk" > $tmp/out
>>>
>> > [...]
>>
>>  I have built binary packages for "sed" and "gawk", created in a machine
>>> with the same characteristics and configuration, and emerged those to
>>> the new machine.  Even so, the errors keep coming.
>>>
>>
>> It could be an issue with faulty memory, or problem with glibc.
>>
>> Often though, illegal instruction is the result of a mismatch between the
>> host, and the target for which the binary was compiled.
>> This could be checked by comparing /proc/cpuinfo with your CFLAGs.
>>
>>
>>
> Thanks, gonna check that.
>
> Francisco
>


You were right.  I have overlooked the type of the new machine's CPU (it is
a "Pentium(R) Dual-Core  CPU" and the other one, already working, is a
"Intel(R) Core(TM)2 Duo CPU"). So, a "march=nocona" instead of a
"march=core2" seems to have solved the problem.

Thank you!
Francisco

[-- Attachment #2: Type: text/html, Size: 2523 bytes --]

Re: [gentoo-user] Re: emerge -e errors right after install

[Walter Dnes]

On Fri, Aug 16, 2013 at 03:18:35PM -0300, Francisco Ares wrote

> You were right.  I have overlooked the type of the new machine's CPU (it is
> a "Pentium(R) Dual-Core  CPU" and the other one, already working, is a
> "Intel(R) Core(TM)2 Duo CPU"). So, a "march=nocona" instead of a
> "march=core2" seems to have solved the problem.

  I have the following in make.conf

CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -fno-unwind-tables -fno-asynchronous-unwind-tables"
CXXFLAGS="${CFLAGS}"

...where "-march=native" will always work correctly for a local build.
The only possible worry is if you're cross-compiling and or distributing
a binary to multiple machines.  It also saves me the headache of
figuring out the CFLAGS setting whenever I get a new machine.  You still
have to set up the correct processor in the kernel, however.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

[gentoo-user] Re: emerge -e errors right after install

[Michael Palimaka]

On 17/08/2013 08:38, Walter Dnes wrote:
>
>    I have the following in make.conf
>
> CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -fno-unwind-tables -fno-asynchronous-unwind-tables"
> CXXFLAGS="${CFLAGS}"
>
> ...where "-march=native" will always work correctly for a local build.
> The only possible worry is if you're cross-compiling and or distributing
> a binary to multiple machines.  It also saves me the headache of
> figuring out the CFLAGS setting whenever I get a new machine.  You still
> have to set up the correct processor in the kernel, however.
>

While -march=native is generally good advice, GCC is not perfect and on 
occasion it can flags to be enabled that are not supported, resulting in 
the invalid instruction error.

Re: [gentoo-user] Re: emerge -e errors right after install

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

2013/8/17 Michael Palimaka <kensington@gentoo.org>

> On 17/08/2013 08:38, Walter Dnes wrote:
>
>>
>>    I have the following in make.conf
>>
>> CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -fno-unwind-tables
>> -fno-asynchronous-unwind-**tables"
>> CXXFLAGS="${CFLAGS}"
>>
>> ...where "-march=native" will always work correctly for a local build.
>> The only possible worry is if you're cross-compiling and or distributing
>> a binary to multiple machines.  It also saves me the headache of
>> figuring out the CFLAGS setting whenever I get a new machine.  You still
>> have to set up the correct processor in the kernel, however.
>>
>>
> While -march=native is generally good advice, GCC is not perfect and on
> occasion it can flags to be enabled that are not supported, resulting in
> the invalid instruction error.
>
>
>
Thanks, that is a good point to be aware of.

Francisco

[-- Attachment #2: Type: text/html, Size: 1481 bytes --]

Re: [gentoo-user] Re: emerge -e errors right after install

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]

2013/8/16 Walter Dnes <waltdnes@waltdnes.org>

> On Fri, Aug 16, 2013 at 03:18:35PM -0300, Francisco Ares wrote
>
> > You were right.  I have overlooked the type of the new machine's CPU (it
> is
> > a "Pentium(R) Dual-Core  CPU" and the other one, already working, is a
> > "Intel(R) Core(TM)2 Duo CPU"). So, a "march=nocona" instead of a
> > "march=core2" seems to have solved the problem.
>
>   I have the following in make.conf
>
> CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -fno-unwind-tables
> -fno-asynchronous-unwind-tables"
> CXXFLAGS="${CFLAGS}"
>
> ...where "-march=native" will always work correctly for a local build.
> The only possible worry is if you're cross-compiling and or distributing
> a binary to multiple machines.  It also saves me the headache of
> figuring out the CFLAGS setting whenever I get a new machine.  You still
> have to set up the correct processor in the kernel, however.
>
> --
> Walter Dnes <waltdnes@waltdnes.org>
> I don't run "desktop environments"; I run useful applications
>
>
Yes, that is the problem. I got the oldest CPU on witch the same binaries
will run. The newest uses an Intel I3, but the oldest ones run on a "Dual
Core" (not "Core-2", as my first assumption).

Thanks for the other parameters though, I have never tried them. Gonna take
a look.

Francisco

[-- Attachment #2: Type: text/html, Size: 2061 bytes --]

Re: [gentoo-user] emerge -e errors right after install

[Stroller]

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]


On 16 August 2013, at 14:22, Francisco Ares wrote:
> ...
> But (here comes the "but"), right on the point I was able to build the kernel ... I tried an "emerge -e world", and there were so many errors that very few packages were able to be completely built.

Is this during the installation process?

IMO you should exit the chroot and get the system booting before you try re-emerging everything.

Stroller.
 

[-- Attachment #2: Type: text/html, Size: 835 bytes --]

Re: [gentoo-user] emerge -e errors right after install

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

2013/8/17 Stroller <stroller@stellar.eclipse.co.uk>

>
> On 16 August 2013, at 14:22, Francisco Ares wrote:
>
> ...
> But (here comes the "but"), right on the point I was able to build the
> kernel ... I tried an "emerge -e world", and there were so many errors that
> very few packages were able to be completely built.
>
>
> Is this during the installation process?
>
> IMO you should exit the chroot and get the system booting before you try
> re-emerging everything.
>
> Stroller.
>
>

Yes, after a bunch of "/etc/" settings, including network, locale, keyboard
layout, ..., but before building the kernel.

I think this time the kernel had no effect, since the "stage-3" was working
perfectly, and then, during "emerge -e", some applications started to
malfunction, and returned to work after a "march" change.

Thanks to your contribution
Francisco

[-- Attachment #2: Type: text/html, Size: 1714 bytes --]