Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
2.6 Kernel (and headers) + NPTL Guide
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3, 4, 5  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
ka0ttic
Retired Dev
Retired Dev


Joined: 23 Oct 2003
Posts: 46
Location: Ormond Beach, FL

PostPosted: Sun Feb 15, 2004 2:09 am    Post subject: 2.6 Kernel (and headers) + NPTL Guide Reply with quote

2.6 Kernel (and headers) + NPTL Guide

Introduction

This guide will attempt to give instructions on doing a fresh install from stage 1 using 2.6 headers and the nptl USE flag set. Beware that this is still considered testing/unstable, so use at your own risk. Instead of repeating basic installation steps, I will refer to the Gentoo 1.4 Installation Instructions: http://www.gentoo.org/doc/en/gentoo-x86-install.xml.


make.conf

Follow all installation instructions until you get to the section on editing make.conf. Add nptl to the USE flags along with whatever else you use. This is the only thing different you need to do with make.conf.


Editing the linux-headers ebuild

At the time of this writing, the most current 2.6 headers ebuild is linux-headers-2.6.1.

Code:
# nano /usr/portage/sys-kernel/linux-headers/linux-headers-2.6.1.ebuild


Find the line that says KEYWORDS="-*" and change to:

Code:
KEYWORDS="-* x86"



Starting the bootstrap process

The most annoying part of installing Gentoo, IMO (Especially the time I installed Gentoo from stage 1 on a P233). Anyways, to start the bootstrap process, type:

Code:
# /usr/portage/scripts/bootstrap-2.6.sh


Go find something to do for a while, but I would recommend checking back every once in a while just to make sure its still chugging along (like the time a bootstrap failed 5 minutes after I started it and went to bed :) ).


emerge system

Just a few notes on stage 2.

1. Add the following to make.conf:

Code:
ACCEPT_KEYWORDS="~x86"


You must do this in order to compile some programs with 2.6 headers.

2. The last couple of time I have done this, emerge system failed while compiling iputils. For some reason a couple dependencies weren't installed first. If it fails, try emerge flex (it complains abow -lfl not existing). I also found that it will fail because autoconf isn't installed yet, so emerge autoconf. Then continue with emerge system.

Follow the rest of the installation instructions. NOTE: don't forget to install a 2.6 kernel


First boot

Hopefully the install went smoothly. The first thing I would recommend that you do is re-emerge glibc, so that NPTL support will be compiled in. I didn't realize this at first (I thought that because I had nptl in the use flags before bootstrap, that it would built it with NPTL support). You can check by running:

Code:

# /lib/libc.so.6

GNU C Library stable release version 2.3.3, by Roland McGrath et al.Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR
A PARTICULAR PURPOSE.
Compiled by GNU CC version 3.3.2 20040119 (Gentoo Linux 3.3.2-r7, propolice-3.3-7).
Compiled on a Linux 2.6.1 system on 2004-02-13.
Available extensions:
     GNU libio by Per Bothner       
     crypt add-on version 2.1 by Michael Glad and others       
     NPTL 0.60 by Ulrich Drepper       
     BIND-8.2.3-T5B       
     NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
     Thread-local storage support included.
Report bugs using the `glibcbug' script to <bugs@gnu.org>.


Notice the line NPTL 0.60 by Uldrich Drepper. This means that glibc has NPTL support enabled. If you do not see this (and instead see linux-threads), re-emerge glibc and remember to make sure that the nptl USE flag is set.


Hint

If you are unable to get some package to compile successfully, make sure you look in the ebuild directory for that package, to see if there is a newer ebuild. Just because ACCEPT_KEYWORDS is set to ~x86 doesn't mean there isn't a newer version. Some ebuilds (for example, linux-headers-2.6.1) are unmasked for everything.

Any problems, feedback, corrections, etc are encrouraged.

Have fun.

--
Aaron
Back to top
View user's profile Send private message
snakattak3
Guru
Guru


Joined: 11 Dec 2002
Posts: 468
Location: Seattle

PostPosted: Sun Feb 15, 2004 3:04 am    Post subject: Reply with quote

If you don't want to do a fresh install, can you just put USE="nptl" and emerge glibc?
_________________
Ban Reality TV!
Adopt an Unanswered Post
Back to top
View user's profile Send private message
ka0ttic
Retired Dev
Retired Dev


Joined: 23 Oct 2003
Posts: 46
Location: Ormond Beach, FL

PostPosted: Sun Feb 15, 2004 3:18 am    Post subject: Reply with quote

Quote:

If you don't want to do a fresh install, can you just put USE="nptl" and emerge glibc?


I've never done it that way, so I cannot say for sure. I'm sure the system would still work, but I do not know if you can use NPTL w/o using the 2.6 headers. Maybe someone a little more knowledgable can extend on that?
Back to top
View user's profile Send private message
Deepu Sudhakar
Tux's lil' helper
Tux's lil' helper


Joined: 30 Aug 2003
Posts: 84

PostPosted: Sun Feb 15, 2004 4:20 am    Post subject: Reply with quote

ka0ttic wrote:
Quote:

If you don't want to do a fresh install, can you just put USE="nptl" and emerge glibc?


I've never done it that way, so I cannot say for sure. I'm sure the system would still work, but I do not know if you can use NPTL w/o using the 2.6 headers. Maybe someone a little more knowledgable can extend on that?

I've been using NPTL without the 2.6 headers, and I haven't run into any problems. Still...I'm not sure if there are any adverse effects to this setup.
Back to top
View user's profile Send private message
Cerement
Guru
Guru


Joined: 14 Jun 2003
Posts: 404

PostPosted: Sun Feb 15, 2004 4:55 am    Post subject: Reply with quote

seen several arguments back and forth over whether you need 2.6 headers or to just be running a 2.6 kernel -- currently, I'm of the latter opinion, someone else in another nptl thread pointed out a way to do a quick check:
Code:
# /lib/libc.so.6
should return several lines including:
Code:
Available extensions:
        ...
        NPTL 0.60 by Ulrich Drepper
        ...
Before I had enabled nptl, this line read linuxthreads by ...
Back to top
View user's profile Send private message
corefile
n00b
n00b


Joined: 27 Jun 2002
Posts: 44

PostPosted: Sun Feb 15, 2004 8:50 am    Post subject: Reply with quote

what is nptl?
Back to top
View user's profile Send private message
Boris27
Guru
Guru


Joined: 05 Nov 2003
Posts: 562
Location: Almelo, The Netherlands

PostPosted: Sun Feb 15, 2004 12:49 pm    Post subject: Reply with quote

native posix threading library.

its a way to handle concurrent processes. it appears to be a bit faster than the linuxthreads system that has been used so far.
Back to top
View user's profile Send private message
jpalko
n00b
n00b


Joined: 12 Mar 2003
Posts: 65
Location: Piispanristi, Finland

PostPosted: Mon Feb 16, 2004 7:48 am    Post subject: Tried to follow, but... Reply with quote

I got stuck at the point where:
Code:
>>> emerge (1 of 34) net-misc/iputils-021109-r1 to /
>>> md5 src_uri ;-) iputils-ss021109-try.tar.bz2
>>> Unpacking source...
>>> Unpacking iputils-ss021109-try.tar.bz2 to /portage/tmp/portage/iputils-021109-r1/work
ipv6
>>> Source unpacked.
...
parse.y: In function `setkeymsg':
parse.y:635: warning: dereferencing type-punned pointer will break strict-aliasing rules
parse.y:651: warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc -o setkey setkey.o parse.o token.o pfkey.o pfkey_dump.o key_debug.o ipsec_strerror.o -L../libipsec -lipsec -lfl
rm token.c
configure.in:1: error: possibly undefined macro: dnl
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:138: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS'

!!! ERROR: net-misc/iputils-021109-r1 failed.
!!! Function src_compile, Line 52, Exitcode 1
!!! (no error message)

Any ideas on how to proceed as this did not aid me: Bug #38774?
_________________
Jukka Palko
Piispanristi, Finland
Linux Counter ID #219161
Back to top
View user's profile Send private message
GurliGebis
Retired Dev
Retired Dev


Joined: 08 Aug 2002
Posts: 509

PostPosted: Mon Feb 16, 2004 9:02 am    Post subject: Re: Tried to follow, but... Reply with quote

jpalko wrote:
I got stuck at the point where:
Code:
>>> emerge (1 of 34) net-misc/iputils-021109-r1 to /
>>> md5 src_uri ;-) iputils-ss021109-try.tar.bz2
>>> Unpacking source...
>>> Unpacking iputils-ss021109-try.tar.bz2 to /portage/tmp/portage/iputils-021109-r1/work
ipv6
>>> Source unpacked.
...
parse.y: In function `setkeymsg':
parse.y:635: warning: dereferencing type-punned pointer will break strict-aliasing rules
parse.y:651: warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc -o setkey setkey.o parse.o token.o pfkey.o pfkey_dump.o key_debug.o ipsec_strerror.o -L../libipsec -lipsec -lfl
rm token.c
configure.in:1: error: possibly undefined macro: dnl
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:138: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS'

!!! ERROR: net-misc/iputils-021109-r1 failed.
!!! Function src_compile, Line 52, Exitcode 1
!!! (no error message)

Any ideas on how to proceed as this did not aid me: Bug #38774?


I know it is a difficult way to do it, but try this:
Code:
emerge system -p

and then emerge every package you can (one by one), and then emerge system when done (to install the packages that failed before), thats how I did it.
_________________
Queen Rocks.
Back to top
View user's profile Send private message
ka0ttic
Retired Dev
Retired Dev


Joined: 23 Oct 2003
Posts: 46
Location: Ormond Beach, FL

PostPosted: Mon Feb 16, 2004 10:19 am    Post subject: Reply with quote

Quote:

!!! ERROR: net-misc/iputils-021109-r1 failed.
!!! Function src_compile, Line 52, Exitcode 1
!!! (no error message)


Did you not read my whole post? You need to emerge flex and go ahead and emerge autoconf because it will fail on that too.. then reissue the emerge system command.

--
Aaron
Back to top
View user's profile Send private message
jpalko
n00b
n00b


Joined: 12 Mar 2003
Posts: 65
Location: Piispanristi, Finland

PostPosted: Mon Feb 16, 2004 10:23 am    Post subject: Reply with quote

ka0ttic wrote:
Quote:

!!! ERROR: net-misc/iputils-021109-r1 failed.
!!! Function src_compile, Line 52, Exitcode 1
!!! (no error message)


Did you not read my whole post? You need to emerge flex and go ahead and emerge autoconf because it will fail on that too.. then reissue the emerge system command.

--
Aaron


Tried it, did not work... :(
_________________
Jukka Palko
Piispanristi, Finland
Linux Counter ID #219161
Back to top
View user's profile Send private message
ka0ttic
Retired Dev
Retired Dev


Joined: 23 Oct 2003
Posts: 46
Location: Ormond Beach, FL

PostPosted: Mon Feb 16, 2004 10:31 am    Post subject: Reply with quote

Sorry, I failed to check out the link to bugs.gentoo.org until AFTER I posted. My apologies. I didn't seem to have any problems with openssl.. If you have tried emerging those 3 and then re-doing emerge system, to no avail, then I don't really know what else to tell you other than to do what the other poster said and manually emerging everything.

--
Aaron
Back to top
View user's profile Send private message
jpalko
n00b
n00b


Joined: 12 Mar 2003
Posts: 65
Location: Piispanristi, Finland

PostPosted: Mon Feb 16, 2004 10:41 am    Post subject: Reply with quote

Oh well, I started the installation from beginning, now doing bootstrap-2.6.sh. I propably messed up somethings on my machine last time, so will see how things go now with it. :)
_________________
Jukka Palko
Piispanristi, Finland
Linux Counter ID #219161
Back to top
View user's profile Send private message
GurliGebis
Retired Dev
Retired Dev


Joined: 08 Aug 2002
Posts: 509

PostPosted: Mon Feb 16, 2004 11:06 am    Post subject: Reply with quote

If emerge system fails again, then try my methode.
_________________
Queen Rocks.
Back to top
View user's profile Send private message
jpalko
n00b
n00b


Joined: 12 Mar 2003
Posts: 65
Location: Piispanristi, Finland

PostPosted: Mon Feb 16, 2004 3:28 pm    Post subject: Reply with quote

This try it got stuck at iputils again, to which merging:
Code:
# emerge autoconf flex
# emerge system

helped. Whonder what went wrong last time... I know for sure that I merged autoconf and flex both on last attempt as well, but I must have been tired in the evening and messed up something. :wink: This time though I used the newest experimental stage1 tarball...

Currently proceeding on
Code:
emerge (15 of 54) sys-fs/e2fsprogs-1.34-r1 to /


Looking good. :-)

The machine got stuck while doing genkernel all, so I had to push reset on the machine during it and continue from that after restarting the installation. Interesting effect, but it could have been caused by the old hard disc from which I had a partition mounted and it had started to have a lot of UncorrectableError's in messages...

Definite success:
Code:
$ /lib/libc.so.6
GNU C Library stable release version 2.3.3, by Roland McGrath et al.
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.3.2 20040119 (Gentoo Linux 3.3.2-r7, propolice-3.3-7).
Compiled on a Linux 2.6.1 system on 2004-02-16.
Available extensions:
        GNU libio by Per Bothner
        crypt add-on version 2.1 by Michael Glad and others
        NPTL 0.60 by Ulrich Drepper
        BIND-8.2.3-T5B
        NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
Report bugs using the `glibcbug' script to <bugs@gnu.org>.

_________________
Jukka Palko
Piispanristi, Finland
Linux Counter ID #219161
Back to top
View user's profile Send private message
ka0ttic
Retired Dev
Retired Dev


Joined: 23 Oct 2003
Posts: 46
Location: Ormond Beach, FL

PostPosted: Tue Feb 17, 2004 12:48 am    Post subject: Reply with quote

jpalko,

Glad to see ya got it up and running :D I almost have my machine back to the way 'twas before reinstalling... (I wrote the guide write after I did it). Anyways, glad you got it working.

--
Aaron
Back to top
View user's profile Send private message
jpalko
n00b
n00b


Joined: 12 Mar 2003
Posts: 65
Location: Piispanristi, Finland

PostPosted: Tue Feb 17, 2004 9:16 am    Post subject: Got stuck again... :) Reply with quote

It appears that Bug #41856 is on the way to my completion in installation. Though I have a feeling that it is a duplicate of Bug #35088 in a way or another...

Well, but my bit onto the bug information in order to aid the cause. :wink:

Code:
>>> emerge (7 of 105) sys-apps/eject-2.0.13 to /
>>> md5 src_uri ;-) eject-2.0.13.tar.gz
>>> Unpacking source...
>>> Unpacking eject-2.0.13.tar.gz to /portage/tmp/portage/eject-2.0.13/work
 * Applying eject-2.0.13-kernel25-support.patch...                                                                                                                                                                                             [ ok ]
>>> Source unpacked.
creating cache ./config.cache
checking for a BSD compatible install... /bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... gcc
checking whether the C compiler (gcc -mcpu=athlon-xp -march=athlon-xp -msse -mmmx -m3dnow -O2 -fomit-frame-pointer -frerun-loop-opt -pipe ) works... yes
checking whether the C compiler (gcc -mcpu=athlon-xp -march=athlon-xp -msse -mmmx -m3dnow -O2 -fomit-frame-pointer -frerun-loop-opt -pipe ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for fcntl.h... yes
checking for sys/ioctl.h... yes
checking for unistd.h... yes
checking for working const... yes
checking for regcomp... yes
checking for strdup... yes
checking for strerror... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
Making all in po
make[1]: Entering directory `/portage/tmp/portage/eject-2.0.13/work/eject-2.0.13/po'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/portage/tmp/portage/eject-2.0.13/work/eject-2.0.13/po'
make[1]: Entering directory `/portage/tmp/portage/eject-2.0.13/work/eject-2.0.13'
gcc -DPACKAGE=\"eject\" -DVERSION=\"2.0.13\" -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_REGCOMP=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1  -I. -I.   -I/usr/src/linux -I/usr/src/linux/include -DDEFAULTDEVICE=\"cdrom\" -DGETOPTLONG  -Wall -O3  -mcpu=athlon-xp -march=athlon-xp -msse -mmmx -m3dnow -O2 -fomit-frame-pointer -frerun-loop-opt -pipe -c eject.c
gcc -DPACKAGE=\"eject\" -DVERSION=\"2.0.13\" -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_UNISTD_H=1 -DHAVE_REGCOMP=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1  -I. -I.   -I/usr/src/linux -I/usr/src/linux/include -DDEFAULTDEVICE=\"cdrom\" -DGETOPTLONG  -Wall -O3  -mcpu=athlon-xp -march=athlon-xp -msse -mmmx -m3dnow -O2 -fomit-frame-pointer -frerun-loop-opt -pipe -c volname.c
volname.c: In function `main':
volname.c:58: warning: implicit declaration of function `exit'
gcc -Wall -O3  -mcpu=athlon-xp -march=athlon-xp -msse -mmmx -m3dnow -O2 -fomit-frame-pointer -frerun-loop-opt -pipe  -o volname  volname.o 
In file included from /usr/src/linux/include/linux/cdrom.h:14,
                 from eject.c:68:
/usr/src/linux/include/asm/byteorder.h:14: error: syntax error before "__u32"
/usr/src/linux/include/asm/byteorder.h:28: error: syntax error before "__u64"
In file included from /usr/src/linux/include/linux/byteorder/little_endian.h:11,
                 from /usr/src/linux/include/asm/byteorder.h:57,
                 from /usr/src/linux/include/linux/cdrom.h:14,
                 from eject.c:68:
/usr/src/linux/include/linux/byteorder/swab.h:133: error: syntax error before "__u16"
/usr/src/linux/include/linux/byteorder/swab.h:146: error: syntax error before "__u32"
/usr/src/linux/include/linux/byteorder/swab.h:160: error: syntax error before "__u64"
make[1]: *** [eject.o] Error 1
make[1]: Leaving directory `/portage/tmp/portage/eject-2.0.13/work/eject-2.0.13'
make: *** [all-recursive] Error 1

!!! ERROR: sys-apps/eject-2.0.13 failed.
!!! Function src_compile, Line 418, Exitcode 2
!!! emake failed

_________________
Jukka Palko
Piispanristi, Finland
Linux Counter ID #219161
Back to top
View user's profile Send private message
ka0ttic
Retired Dev
Retired Dev


Joined: 23 Oct 2003
Posts: 46
Location: Ormond Beach, FL

PostPosted: Tue Feb 17, 2004 10:21 am    Post subject: Reply with quote

Quote:

It appears that Bug #41856 is on the way to my completion in installation. Though I have a feeling that it is a duplicate of Bug #35088 in a way or another...


Yeah, I had this problem too.. looks like it doesn't get along with 2.6 headers. I just injected the package for now so I could get gnome installed. I'll have to try out that 2.6 patch when I get a chance.
Back to top
View user's profile Send private message
jpalko
n00b
n00b


Joined: 12 Mar 2003
Posts: 65
Location: Piispanristi, Finland

PostPosted: Tue Feb 17, 2004 10:26 am    Post subject: Reply with quote

Decided to skip compiling gnome required packages and just compile the normal setup of gdm + xfree + fvwm2, which seem to go okay.

DirectFB needed this for compiling (I have a nvidia based card, some others appear to have problems still)
Code:
# VIDEO_CARDS=nvidia emerge DirectFB

The following get stuck on my compilation attempts:
    -aalib fails in the beginning
    Code:
    # emerge xine-ui
    ...
    cd . && autoconf
    FATAL ERROR: Autoconf version 2.50 or higher is required for this script
    make: *** [configure] Error 2
    make: *** Waiting for unfinished jobs....

    !!! ERROR: media-libs/aalib-1.4_rc4-r2 failed.
    !!! Function src_compile, Line 52, Exitcode 2
    !!! (no error message)

    # emerge -s autoconf
    ...
    *  sys-devel/autoconf
          Latest version available: 2.59-r2
          Latest version installed: 2.59-r2
          Size of downloaded files: 1,336 kB
          Homepage:    http://www.gnu.org/software/autoconf/autoconf.html
          Description: Used to create autoconfiguration files
          License:     GPL-2

    -alsa-tools gets pretty far, but fails on
    Code:
    In file included from /lib/modules/2.6.3-rc3/build/include/sound/ainstr_fm.h:29,
                     from sbiload.c:23:
    /lib/modules/2.6.3-rc3/build/include/asm/byteorder.h:14: error: syntax error before "__u32"
    /lib/modules/2.6.3-rc3/build/include/asm/byteorder.h:28: error: syntax error before "__u64"
    In file included from /lib/modules/2.6.3-rc3/build/include/linux/byteorder/little_endian.h:11,
                     from /lib/modules/2.6.3-rc3/build/include/asm/byteorder.h:57,
                     from /lib/modules/2.6.3-rc3/build/include/sound/ainstr_fm.h:29,
                     from sbiload.c:23:
    /lib/modules/2.6.3-rc3/build/include/linux/byteorder/swab.h:133: error: syntax error before "__u16"
    /lib/modules/2.6.3-rc3/build/include/linux/byteorder/swab.h:146: error: syntax error before "__u32"
    /lib/modules/2.6.3-rc3/build/include/linux/byteorder/swab.h:160: error: syntax error before "__u64"
    make: *** [sbiload.o] Error 1

    !!! ERROR: media-sound/alsa-tools-1.0.2 failed.
    !!! Function src_compile, Line 51, Exitcode 2
    !!! make failed

_________________
Jukka Palko
Piispanristi, Finland
Linux Counter ID #219161
Back to top
View user's profile Send private message
jpalko
n00b
n00b


Joined: 12 Mar 2003
Posts: 65
Location: Piispanristi, Finland

PostPosted: Tue Feb 17, 2004 12:05 pm    Post subject: Reply with quote

jpalko wrote:
Code:
# emerge xine-ui
...
cd . && autoconf
FATAL ERROR: Autoconf version 2.50 or higher is required for this script
make: *** [configure] Error 2
make: *** Waiting for unfinished jobs....

!!! ERROR: media-libs/aalib-1.4_rc4-r2 failed.
!!! Function src_compile, Line 52, Exitcode 2
!!! (no error message)

# emerge -s autoconf
...
*  sys-devel/autoconf
      Latest version available: 2.59-r2
      Latest version installed: 2.59-r2
      Size of downloaded files: 1,336 kB
      Homepage:    http://www.gnu.org/software/autoconf/autoconf.html
      Description: Used to create autoconfiguration files
      License:     GPL-2


Quoting myself, this was already fixed with Bug #40926.
_________________
Jukka Palko
Piispanristi, Finland
Linux Counter ID #219161
Back to top
View user's profile Send private message
GTVincent
Tux's lil' helper
Tux's lil' helper


Joined: 26 Oct 2002
Posts: 91
Location: Las Vegas, NV

PostPosted: Tue Feb 17, 2004 1:07 pm    Post subject: Reply with quote

I have had success building a gentoo system with the 2.6 kernel-headers from stage 1, using the experimental livecd and stage1-x86-20040128.tar.bz2. The only package I've had to emerge with ~x86 was xfsprogs. system and Gnome emerged without a problem.on a Dell Dimension 4550.

[make.conf[
USE="-qt -kde -arts nptl gtk2"
CFLAGS="-O3 -mcpu=pentium4 -mmmx -pipe -msse -msse2 -mfpmath=sse -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CSSFLAGS=$CXXFLAGS
Back to top
View user's profile Send private message
sebweb
Apprentice
Apprentice


Joined: 29 Jan 2003
Posts: 220
Location: Bordeaux - France

PostPosted: Tue Feb 17, 2004 6:13 pm    Post subject: Reply with quote

I have this :
Quote:

# /lib/libc-2.3.2.so
Inconsistency detected by ld.so: rtld.c: 1252: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev->l_next == _rtld_local._dl_rtld_map.l_next' failed!


glibc compiled with ntpl use flag.
What does it mean ?
Back to top
View user's profile Send private message
sekh
n00b
n00b


Joined: 20 Dec 2002
Posts: 55

PostPosted: Tue Feb 17, 2004 10:31 pm    Post subject: Reply with quote

i'm running into this problem too:

Code:
configure.in:1: error: possibly undefined macro: dnl
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:138: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS'

!!! ERROR: net-misc/iputils-021109-r1 failed.
!!! Function src_compile, Line 52, Exitcode 1
!!! (no error message)

I've tried emerging flex and autoconf too. That didn't help the problem it keeps coming up. ACCEPT_KEYWORDS are set to ~x86

Like jpalko i've also checked out the bug in bugzilla, unfortunately the info in there didn't help either :-(

Any ideas on what can be done to get around this?
Back to top
View user's profile Send private message
sekh
n00b
n00b


Joined: 20 Dec 2002
Posts: 55

PostPosted: Tue Feb 17, 2004 10:50 pm    Post subject: Reply with quote

ok, i wasn't about to let some borked sourcecode for unstable ebuild of ip utils stop my install.

Apparently the old iputils-020927.ebuild works fine for me. So i went ahead and edited the two files
/usr/portage/net-misc/iputils/iputils-021109-r1.ebuild
/usr/portage/net-misc/iputils/iputils-021109.ebuild
removing ~x86 from the keyword listing in each.
This makes portage take the old 020927 version instead which works
i let emerge system run and then it installs this old version without any problems. Now i just hope that wont come back to bite me in the ass later :P

After letting emerge system pass the iputils thing, i redited the two ebuilds putting ~x86 into the keywords list again.

This workaround seems ok for me so far (still emerging, it might fuck up later), but i guess as soon as my system gets running and i do an emerge -u world, it'll want to upgrade ip utils to the fubar versions again.

Does anyone know a solution to this, or do we just have to pray for an updated ebuild which doesn't have these errors?
Back to top
View user's profile Send private message
yamakawa
Guru
Guru


Joined: 28 Jul 2003
Posts: 340

PostPosted: Wed Feb 18, 2004 8:15 am    Post subject: Reply with quote

Another success report w/o 2.6 headers, not from scratch.
I am using sys-kernel/linux-headers-2.4.22.
Code:
# uname -r
2.6.3-rc3

Still I get
Code:
# /lib/libc.so.6
GNU C Library stable release version 2.3.3, by Roland McGrath et al.
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.3.2 20040119 (Gentoo Linux 3.3.2-r7, propolice-3.3-7).
Compiled on a Linux 2.6.2 system on 2004-02-09.
Available extensions:
        GNU libio by Per Bothner
        crypt add-on version 2.1 by Michael Glad and others
        NPTL 0.60 by Ulrich Drepper
        BIND-8.2.3-T5B
        NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
Report bugs using the `glibcbug' script to <bugs@gnu.org>.

All I did was just jump into 2.6 kernels, emerged glibc w/ nptl flag set. :wink:
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page 1, 2, 3, 4, 5  Next
Page 1 of 5

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum