



I would never prelinkaldo_a wrote:hiz and first of all a big thanks for this spectacullar guide!
I just have one question. Does anybody have tried to prelink after following the guide?
After had i completed the basic installation like a charm and also installed kdebase & fvwm i tried to prelink and everything went wrong!! prelink finished with an error msg about libc.so.6 (dont rember rigth now the exact msg) and after that nothing was working. I restarted and got a kernel panic with an error msg smth like "out of bounds madness ... /lib/ld-linux.so.2: undefined symbol : _r_debug". I even tried to chroot using the cd but i got the same msg again. Now i am installing rigth from the beginning!!
I suspect that the problem has smth to do with prelink and glibc but i am not quite sure.
Anyone has any clue?
Hehe ty for the response!! I ll have that in mind for the next time : )!!cheater1034 wrote:I would never prelinkExpecially when using this guide.
The LDFLAGS are linker flags, and particulary the -Bdirect flag is a way better method to prelink. It is not pre-linking but it is like it. When using LDFLAGS, don't prelinkParticulary with -Bdirect, there is no need to prelink. (prelink is a myth :-p, ldflags are not)
Code: Select all
daTenSchLeuDer ~ # emerge --emptytree world
Calculating world dependencies... done!
Traceback (most recent call last):
File "/usr/bin/emerge", line 3263, in ?
if "resume" in portage.mtimedb and \
KeyError: 'mergelist'

Looks like you somehow broke your portage :X I am unsure how to fix that specific /usr/bin/emerge error, I would look for a .tbz2 of portage, and extract it in / and see if it fixes it.moeeeep wrote:Hi
Thanks for this great Conrad guide. But I've run in a problem here.
I have portage 2.1_pre6 installed here and did a emerge --sync before.Code: Select all
daTenSchLeuDer ~ # emerge --emptytree world Calculating world dependencies... done! Traceback (most recent call last): File "/usr/bin/emerge", line 3263, in ? if "resume" in portage.mtimedb and \ KeyError: 'mergelist'
Do you have a suggestion, because I can't update portage either (same problem as above).
Code: Select all
/var/tmp/portage/binutils-2.16.91.0.6/work/binutils-2.16.91.0.6/bfd/elf32-hppa.c:438: error: for each function it appears in.)
make[4]: *** [elf32-hppa.lo] Error 1
make[4]: Leaving directory `/var/tmp/portage/binutils-2.16.91.0.6/work/build/bfd'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/binutils-2.16.91.0.6/work/build/bfd'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/binutils-2.16.91.0.6/work/build/bfd'
make[1]: *** [all-bfd] Error 2
make[1]: Leaving directory `/var/tmp/portage/binutils-2.16.91.0.6/work/build'
make: *** [all] Error 2
!!! ERROR: sys-devel/binutils-2.16.91.0.6 failed.
Call stack:
ebuild.sh, line 1557: Called dyn_compile
ebuild.sh, line 966: Called src_compile
ebuild.sh, line 1272: Called toolchain-binutils_src_compile
!!! emake failed
!!! If you need support, post the topmost build error, and the call stack if relevant.