can't compile a single thing after enabling testing (solved)

pressh · 2006-05-31 07:26:01

so today I enabled the testing repo and synced with it. From then I cannot compile a single thing.
All configure errors with:

checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.

config.log

In file included from /usr/include/bits/posix1_lim.h:153,
                 from /usr/include/limits.h:145,
                 from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/limits.h:122,
                 from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/syslimits.h:7,
                 from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/limits.h:11,
                 from conftest.cc:13:
/usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file or directory
configure:2131: $? = 1
configure: failed program was:

user · 2006-05-31 08:17:50

cp -R /usr/src/linux-2.6.17-rc5/include /usr

use it at my own risk.

At least it WFM.

PS: look at /usr/lib/libstdc++*.so* symbolic link.

iphitus · 2006-05-31 11:37:30

user: chances are he isnt running the latest rc, and secondly, you are NOT meant to use the includes from the latest kernel. Search google, you'll find such use globally condemned. The best method is to use some more sanitized and stable, often from a much older version.

Please don't spread poor usage.

pressh: ensure your system is fully updated to testing, and that this occurs with a range of PKGBUILDs, then feel free to bug report this.

James

JGC · 2006-05-31 15:00:56

Copying over normal kernel headers isn't a good idea, since the kernel headers are never meant to be used for userspace. Instead, some sanitized kernelheaders are provided by the kernel-headers package.

Pacman shouldn't have removed your kernel-headers with the splitup, that bug has been fixed for ages now. Somehow this did happen on your system. Are you running an older version of pacman? Did you downgrade glibc with force-overwrite and upgrade it to 2.4-2 after that again? I can't think of other explanations than those other two. If these two possible cases aren't suitable in your case, please provide us with a pacman.log so we can find out.

user · 2006-05-31 15:27:34

iphitus wrote:

1>ser: chances are he isnt running the latest rc, and secondly, you are NOT meant to use the includes from the latest kernel. Search google, you'll find such use globally condemned. The best method is to use some more sanitized and stable, often from a much older version.
2>Please don't spread poor usage.

1> yeah yeah it just my example, reader will know how to treat it.

2>sure it poor usage for you, but it works me.
so it works by now, how this can't be the choice??
Please let this be natural choice or patch it.
Before the first kernel-header release, this was only the method, afaik.

pressh · 2006-05-31 15:43:10

JGC wrote:

Are you running an older version of pacman?

no

JGC wrote:

Did you downgrade glibc with force-overwrite and upgrade it to 2.4-2 after that again?

don't think I forced it, but at least I did downgrade it back to 2.3.6-3 (from 2.4-1 (on 05/26/06)). Upgrading to 2.4-1 after that again
yesterday. So probably that's where is did go wrong on my machine

Upgrading kernel-headers installed the missing files.
Thanks for the hint

Arch Linux

#1 2006-05-31 07:26:01

can't compile a single thing after enabling testing (solved)

#2 2006-05-31 08:17:50

Re: can't compile a single thing after enabling testing (solved)

#3 2006-05-31 11:37:30

Re: can't compile a single thing after enabling testing (solved)

#4 2006-05-31 15:00:56

Re: can't compile a single thing after enabling testing (solved)

#5 2006-05-31 15:27:34

Re: can't compile a single thing after enabling testing (solved)

#6 2006-05-31 15:43:10

Re: can't compile a single thing after enabling testing (solved)

Board footer