View previous topic :: View next topic |
Author |
Message |
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2955
|
Posted: Sat Mar 26, 2005 5:05 am Post subject: |
|
|
In that case, it still does as of last week.
Wait, why am I always the one who makes adds the first post to a new page of the thread? or so it seems. |
|
Back to top |
|
|
Sith_Happens Veteran
Joined: 15 Dec 2004 Posts: 1807 Location: The University of Maryland at College Park
|
Posted: Sat Mar 26, 2005 5:06 am Post subject: |
|
|
Bob P wrote: | Sith_Happens wrote: | The only thing I would say about the useflags in the tutorial are that pthreads and ithreads aren't really neccessary. Unless you use the nptlonly flag instead of nptl, then glibc will becompiled twice, once with LinuxThreads support and once with NPTL support, regardless whether you tell it to or not. |
the ithreads USE flag is not set for the benefit of glibc.
at the time that i wrote the Guide, the perl/libperl ebuilds would issue a specific screen warning if ithreads was not set as a USE flag, asking that ithreads be enabled as a USE flag in order to allow perl/libperl to fully support NPTL.
has this changed? | I've done the installation several times with only the nptl flag set, and have recieved no errors from the perl or libperl ebuilds. I guess somebody fixed the problem. However, redundancy won't hurt you in this case. So while I said it isn't really neccessary, you might as well have them just to be safe. _________________ "That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall
Last edited by Sith_Happens on Sat Mar 26, 2005 5:08 am; edited 1 time in total |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2955
|
Posted: Sat Mar 26, 2005 5:08 am Post subject: |
|
|
Sith_Happens wrote: | I've done the installation several times with only the nptl flag set, and have recieved no errors from the perl or libperl ebuilds. I guess somebody fixed the problem. |
Not errors, just information messages on the screen. |
|
Back to top |
|
|
Sith_Happens Veteran
Joined: 15 Dec 2004 Posts: 1807 Location: The University of Maryland at College Park
|
Posted: Sat Mar 26, 2005 5:10 am Post subject: |
|
|
kimchi_sg wrote: | Sith_Happens wrote: | I've done the installation several times with only the nptl flag set, and have recieved no errors from the perl or libperl ebuilds. I guess somebody fixed the problem. |
Not errors, just information messages on the screen. | Hmm, well let me check. _________________ "That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
Back to top |
|
|
Bob P Advocate
Joined: 20 Oct 2004 Posts: 3355 Location: Jackass! Development Labs
|
Posted: Sat Mar 26, 2005 5:14 am Post subject: |
|
|
sys-devel/libperl/libperl-5.8.5.ebuild wrote: | PLEASE NOTE: If you want to compile perl-5.0 with threading enabled, you must restart this emerge with USE=ithreads emerge....
Threading is not supported by all applications that compile against perl. You use threading at your own discretion. |
we're beginning to look like the three stooges. _________________ .
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Last edited by Bob P on Sat Mar 26, 2005 5:16 am; edited 1 time in total |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2955
|
Posted: Sat Mar 26, 2005 5:14 am Post subject: |
|
|
Bob, this time round I think you're too lazy
Fire up Code: | vi /usr/portage/sys-devel/libperl/libperl-5.8.6.ebuild | and I get this 93 lines in:
Code: |
pkg_setup() {
# I think this should rather be displayed if you *have* 'ithreads'
# in USE if it could break things ...
if use ithreads
then
ewarn ""
ewarn "PLEASE NOTE: You are compiling perl-5.8 with"
ewarn "interpreter-level threading enabled."
ewarn "Threading is not supported by all applications "
ewarn "that compile against perl. You use threading at "
ewarn "your own discretion. "
ewarn ""
epause 10
else
ewarn ""
ewarn "PLEASE NOTE: If you want to compile perl-5.8 with"
ewarn "threading enabled , you must restart this emerge"
ewarn "with USE=ithreads emerge...."
ewarn "Threading is not supported by all applications "
ewarn "that compile against perl. You use threading at "
ewarn "your own discretion. "
ewarn ""
epause 10
fi
}
|
|
|
Back to top |
|
|
Sith_Happens Veteran
Joined: 15 Dec 2004 Posts: 1807 Location: The University of Maryland at College Park
|
Posted: Sat Mar 26, 2005 5:16 am Post subject: |
|
|
That's so funny I was just about to post that section of the ebuild. Your one step ahead of me kimchi_sg. It would seem that the warning is actually against having interpreter level threading compiled into perl. Interesante.... _________________ "That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2955
|
Posted: Sat Mar 26, 2005 5:18 am Post subject: |
|
|
In case Bob is not convinced, another snippet from a/m ebuild.
Code: |
src_compile() {
# Perl has problems compiling with -Os in your flags
use uclibc || replace-flags "-Os" "-O2"
# This flag makes compiling crash in interesting ways
filter-flags "-malign-double"
export LC_ALL="C"
local myconf=""
if use ithreads
then
einfo "using ithreads"
mythreading="-multi"
myconf="-Dusethreads ${myconf}"
myarch=$(get_abi_CHOST)
myarch="${myarch%%-*}-linux-thread"
else
myarch=$(get_abi_CHOST)
myarch="${myarch%%-*}-linux"
fi
|
|
|
Back to top |
|
|
Bob P Advocate
Joined: 20 Oct 2004 Posts: 3355 Location: Jackass! Development Labs
|
Posted: Sat Mar 26, 2005 5:18 am Post subject: |
|
|
oh, i was convinced back in january when i wrote the guide.
5.8.6? kimchi_sg, you must be fully "~arch".
i am going to resist the temptation to grep the entire portage tree. _________________ .
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Last edited by Bob P on Sat Mar 26, 2005 5:20 am; edited 1 time in total |
|
Back to top |
|
|
Sith_Happens Veteran
Joined: 15 Dec 2004 Posts: 1807 Location: The University of Maryland at College Park
|
Posted: Sat Mar 26, 2005 5:19 am Post subject: |
|
|
Bob P wrote: | 5.8.6? kimchi_sg, you must be fully "~arch".
i am going to resist the temptation to grep the entire portage tree. | It's the same deal for 5.8.5-r5. Code: | pkg_setup() {
# I think this should rather be displayed if you *have* 'ithreads'
# in USE if it could break things ...
if use ithreads
then
ewarn ""
ewarn "PLEASE NOTE: You are compiling perl-5.8 with"
ewarn "interpreter-level threading enabled."
ewarn "Threading is not supported by all applications "
ewarn "that compile against perl. You use threading at "
ewarn "your own discretion. "
ewarn ""
epause 10
else
ewarn ""
ewarn "PLEASE NOTE: If you want to compile perl-5.8 with"
ewarn "threading enabled , you must restart this emerge"
ewarn "with USE=ithreads emerge...."
ewarn "Threading is not supported by all applications "
ewarn "that compile against perl. You use threading at "
ewarn "your own discretion. "
ewarn ""
fi
|
_________________ "That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall
Last edited by Sith_Happens on Sat Mar 26, 2005 5:19 am; edited 1 time in total |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2955
|
Posted: Sat Mar 26, 2005 5:19 am Post subject: |
|
|
Bob P wrote: | 5.8.6? kimchi_sg, you must be fully "~arch". |
You can check on 5.8.5 ebuild and the text is still there.
Ditto for 5.8.5-r1
Oh, by the way, God bless those who emerge libperl with FEATURES=maketest. Read the ebuild for the juicy explanation. The anti-maketest check (RESTRICT=maketest) does not seem to work though. |
|
Back to top |
|
|
Bob P Advocate
Joined: 20 Oct 2004 Posts: 3355 Location: Jackass! Development Labs
|
|
Back to top |
|
|
Sith_Happens Veteran
Joined: 15 Dec 2004 Posts: 1807 Location: The University of Maryland at College Park
|
Posted: Sat Mar 26, 2005 5:23 am Post subject: |
|
|
Bob P wrote: | i checked 5.8.5 seven posts ago!! | I thought you said you were to lazy to look at the ebuild. _________________ "That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2955
|
Posted: Sat Mar 26, 2005 5:23 am Post subject: |
|
|
But you said you were "too lazy to look in the ebuild"?! |
|
Back to top |
|
|
Sith_Happens Veteran
Joined: 15 Dec 2004 Posts: 1807 Location: The University of Maryland at College Park
|
Posted: Sat Mar 26, 2005 5:23 am Post subject: |
|
|
kimchi_sg wrote: | But you said you were "too lazy to look in the ebuild"?! |
_________________ "That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
Back to top |
|
|
Bob P Advocate
Joined: 20 Oct 2004 Posts: 3355 Location: Jackass! Development Labs
|
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2955
|
Posted: Sat Mar 26, 2005 5:25 am Post subject: |
|
|
Bob P wrote: | i got motivated. |
Well, it is there. |
|
Back to top |
|
|
Sith_Happens Veteran
Joined: 15 Dec 2004 Posts: 1807 Location: The University of Maryland at College Park
|
Posted: Sat Mar 26, 2005 5:25 am Post subject: |
|
|
Well, point is it seems that compiling perl with -ithreads (the default) is to err on the side of caution. However, since so many people have done the install as per the guide, and no one has reported problems with perl, I think everythings cool. _________________ "That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
Back to top |
|
|
ArchiCAT n00b
Joined: 07 Jan 2005 Posts: 14
|
Posted: Sat Mar 26, 2005 7:04 pm Post subject: |
|
|
I also got Segmentation fault when I try to emerge glibc-2.3.4 (using 3.3.4 toolkit).
But I only use Reiser 3.6. Any hints? And what's overlocking? (If you mean overclocking then I haven't)
Code: |
make[2]: *** [/var/tmp/portage/glibc-2.3.4.20050125-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/nis/nis_call.os] Segmentation fault (core dumped)
|
Bob P wrote: | qbad wrote: | Here's what I got after trying to emerge glibc-2.3.4 (using 3.3.4 toolkit):
Code: | ..../csu/crtn.o
collect2: ld terminated with signal 11 [Segmentation Fault]
make[2]: *** [/var/tmp/portage/glibc-2.3.4.20050125/work/build-default-1686-pc-linux-gnu-linuxthreads/elf/sln] Error 1
...
!!! ERROR: sys-libs/glibc-2.3.4.20050125 failed
!!! Function toolchain-glibc_src_compile, Line 187, Exitcode 2
!!! (no error message)
|
I'm currently trying to do stage 1 NPTL on a 2004.3 stage 3 tarball install, but got the same error while doing just a simple stage 1 bootstrap.
No freaky USE flags, everything as it is in the tutorial.
Athlon XP, Reiser4
Any hints? |
Yes. Don't use Reiser4 with this installation method. Although it is possible to perform a Stage 1/3 installation with Reiser4, quite a few deviations from the guide are necessary and the installation is subject to many potential pitfalls. My recommendation would be to drop Reiser 4. You can't do it with this Guide as it is written, and this Guide doesn't support it.
If you can't live without Reiser 4, you might want to send a PM to DrWoland. IIRC he developed a method of using Reiser 4 with this Guide and ran into many, many problems. He was thinking about writing a new guide to support Stage 1/3 with Reiser 4. That would be a good topic for another thread.
Good Luck.
Another common cause of compiler segfaults is overlocking. Don't do it. |
|
|
Back to top |
|
|
96140 Retired Dev
Joined: 23 Jan 2005 Posts: 1324
|
Posted: Sat Mar 26, 2005 8:20 pm Post subject: |
|
|
ArchiCAT wrote: | I also got Segmentation fault when I try to emerge glibc-2.3.4 (using 3.3.4 toolkit).
But I only use Reiser 3.6. Any hints? And what's overlocking? (If you mean overclocking then I haven't)
Code: |
make[2]: *** [/var/tmp/portage/glibc-2.3.4.20050125-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/nis/nis_call.os] Segmentation fault (core dumped)
|
|
I've heard that there are some problems when trying to compile that version of glibc; it often doesn't, or does so incorrectly and causes more problems down the line. Check Bugzilla to see if anyone's officially reported it yet (like this) or come up with a fix. But you say that you tried to compile it with plain ol' gcc 3.3.x? That's odd. I think that every problem I read about was caused by trying to compile it with gcc 3.4.x.
For now, I'd suggest using the previous version of glibc (2.3.4.20050125), and it's definitely a good idea to compile that version with gcc 3.4.x. Add it to your /etc/portage/package.keywords: Code: | =sys-libs/glibc-2.3.4.20050125 ~x86 |
|
|
Back to top |
|
|
Sith_Happens Veteran
Joined: 15 Dec 2004 Posts: 1807 Location: The University of Maryland at College Park
|
Posted: Sat Mar 26, 2005 8:36 pm Post subject: |
|
|
nightmorph wrote: | ArchiCAT wrote: | I also got Segmentation fault when I try to emerge glibc-2.3.4 (using 3.3.4 toolkit).
But I only use Reiser 3.6. Any hints? And what's overlocking? (If you mean overclocking then I haven't)
Code: |
make[2]: *** [/var/tmp/portage/glibc-2.3.4.20050125-r1/work/build-default-i686-pc-linux-gnu-linuxthreads/nis/nis_call.os] Segmentation fault (core dumped)
|
|
I've heard that there are some problems when trying to compile that version of glibc; it often doesn't, or does so incorrectly and causes more problems down the line. Check Bugzilla to see if anyone's officially reported it yet (like this) or come up with a fix. But you say that you tried to compile it with plain ol' gcc 3.3.x? That's odd. I think that every problem I read about was caused by trying to compile it with gcc 3.4.x.
For now, I'd suggest using the previous version of glibc (2.3.4.20050125), and it's definitely a good idea to compile that version with gcc 3.4.x. Add it to your /etc/portage/package.keywords: Code: | =sys-libs/glibc-2.3.4.20050125 ~x86 |
| This is good advice, last time I installed I compiled with glibc-2.3.4-20050125, and then after upgrading to gcc 3.4.3, upgraded glibc to 2.3.4-20050125-r1. However, if 2.3.4-20050125 compiles, then I would suggest you stick with that version. Aside from some bug fixes, theres not a real reason to upgrade to r1. It's marked testing for a reason. _________________ "That question was less stupid; though you asked it in a profoundly stupid way."
I'm the brains behind Jackass! | Tutorials: Shorewall |
|
Back to top |
|
|
Bob P Advocate
Joined: 20 Oct 2004 Posts: 3355 Location: Jackass! Development Labs
|
Posted: Sat Mar 26, 2005 8:48 pm Post subject: |
|
|
package masking isn't going to help, as ALL (x86 and ~x86) versions of glibc broke this week.
its a glibc problem, not a compiler problem. bugzilla is full of bug reports. evidently, somebody has been tinkering with the ebuilds.
the ebuilds reportedly got fixed a yesterday. i'd emerge --sync and give it another shot. _________________ .
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
Back to top |
|
|
ArchiCAT n00b
Joined: 07 Jan 2005 Posts: 14
|
Posted: Sun Mar 27, 2005 12:40 am Post subject: |
|
|
I dropped the extreme optimization, that is I use
Code: |
CFLAGS="-O2 -march=i686 -mtune=i686 -pipe"
|
and then it successfully compiled glibc-2.3.4.20050125-r1 (now compiling gcc-3.4.3).
Thanks for your help. |
|
Back to top |
|
|
ArchiCAT n00b
Joined: 07 Jan 2005 Posts: 14
|
Posted: Sun Mar 27, 2005 1:45 am Post subject: |
|
|
I'm compiling gcc 3.4.3 using gcc 3.4.3. I saw quite a lot of msg (the compilation does not terminate):
"<file>.gcda not found, execution counts assumed to be zero"
where <file> is the name with .gcda extension. Does it matter? |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2955
|
Posted: Sun Mar 27, 2005 5:50 am Post subject: |
|
|
ArchiCAT wrote: | I'm compiling gcc 3.4.3 using gcc 3.4.3. I saw quite a lot of msg (the compilation does not terminate):
"<file>.gcda not found, execution counts assumed to be zero"
where <file> is the name with .gcda extension. Does it matter? |
No it does not. |
|
Back to top |
|
|
|