Re: NPTL support?
On Fri, 16 Mar 2007, Lauri Leukkunen wrote: > On 3/16/07, T Taneli Vahakangas <[EMAIL PROTECTED]> wrote: > > I have a project (at work, closed source). I can build it with > > debian/etch or sb1. With sb2 it gets stuck (or rather, eats all > > available memory ...) at the first step: > > I don't think it's the toolchain ;) Probably sb2. > > > % autoreconf -i -s --force > > configure.ac:17: warning: AC_PROG_LEX invoked multiple times > > ../../lib/autoconf/programs.m4:779: AC_DECL_YYTEXT is expanded from... > > aclocal.m4:7657: AM_PROG_LEX is expanded from... > > configure.ac:17: the top level > > > > (Here it starts occupying memory. The above messages do NOT > > appear with etch or sb1.) > > Could be a kind of symlink loop, sb2 is not guarded against them and > the mapping thing could create them where there really aren't any. You > could try starting sb2 with --verbose and look at the > buildroot/sb2_mapping.log for any hints at what it's doing. Well, it goes on for a while and then stops. The last lines are: [00_default.lua][.*|grep]: __xstat(/home/taneli/buildroot/home/user/XXX/configure.ac) -> (/home/taneli/buildroot/home/user/XXX/configure.ac) [00_default.lua][.*|grep]: open(/home/taneli/buildroot/home/user/XXX/configure.ac) -> (/home/taneli/buildroot/home/user/XXX/configure.ac) I can't tell if this is a good sign or a bad sign ... > > Suppose I build it with sb1, should it work with glibc2.5? > > Probably. Although I'm not exactly sure what you mean ;) Let me rephrase. Would this work (on N800), or am I going to waste ummm... 10 minutes trying it myself: % cp /bin/ls /media/mmc2/arm-lltc/bin % chroot /media/mmc2/arm-lltc % /bin/ls (Supposing of course that /bin/ls is compiled against glibc2.3 or whatever is in maemo3.0) Taneli ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: NPTL support?
On 3/16/07, T Taneli Vahakangas <[EMAIL PROTECTED]> wrote: I have a project (at work, closed source). I can build it with debian/etch or sb1. With sb2 it gets stuck (or rather, eats all available memory ...) at the first step: I don't think it's the toolchain ;) Probably sb2. % autoreconf -i -s --force configure.ac:17: warning: AC_PROG_LEX invoked multiple times ../../lib/autoconf/programs.m4:779: AC_DECL_YYTEXT is expanded from... aclocal.m4:7657: AM_PROG_LEX is expanded from... configure.ac:17: the top level (Here it starts occupying memory. The above messages do NOT appear with etch or sb1.) Could be a kind of symlink loop, sb2 is not guarded against them and the mapping thing could create them where there really aren't any. You could try starting sb2 with --verbose and look at the buildroot/sb2_mapping.log for any hints at what it's doing. Suppose I build it with sb1, should it work with glibc2.5? Probably. Although I'm not exactly sure what you mean ;) /lauri ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: NPTL support?
Hello, sorry for delay, I was sick, kids were sick ... Quim (& others at nokia): I suppose there's no public ETA for glibc 2.5? Lauri, I haven't tried glibc yet, but the toolchain has some problems: I have a project (at work, closed source). I can build it with debian/etch or sb1. With sb2 it gets stuck (or rather, eats all available memory ...) at the first step: % autoreconf -i -s --force configure.ac:17: warning: AC_PROG_LEX invoked multiple times ../../lib/autoconf/programs.m4:779: AC_DECL_YYTEXT is expanded from... aclocal.m4:7657: AM_PROG_LEX is expanded from... configure.ac:17: the top level (Here it starts occupying memory. The above messages do NOT appear with etch or sb1.) Suppose I build it with sb1, should it work with glibc2.5? Taneli On Mon, 12 Mar 2007, Lauri Leukkunen wrote: > Bleh, damn gmail.. Sent this directly to Taneli, here's the same for > the list as well: > > http://rahina.org/sb2/arm-lltc-gcc412-glibc25.tar.bz2 > > Not just the glibc, but you can extract it from there. The toolchain > itself is built for amd64. > > /lauri > > On 3/12/07, Quim Gil <[EMAIL PROTECTED]> wrote: > > We are going to use glibc 2.5 at some point. This will bring NPTL > > support. > > > > In the meantime... you will need the help of someone more clever than > > me. :) > > > > On Sun, 2007-03-11 at 10:28 +0200, ext T Taneli Vahakangas wrote: > > > where can I find NPTL-enabled libc (for 770 or N800)? If it isn't > > > available already, how would I go about making one? > > -- > > Quim Gil - http://maemo.org > > > > ___ > > maemo-developers mailing list > > maemo-developers@maemo.org > > https://maemo.org/mailman/listinfo/maemo-developers > > > > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
(Flame) Re: NPTL support?
On 3/12/07, Paul Klapperich <[EMAIL PROTECTED]> wrote: On 3/12/07, Kees Jongenburger <[EMAIL PROTECTED]> wrote: > On 3/12/07, Lauri Leukkunen <[EMAIL PROTECTED]> wrote: > > Bleh, damn gmail.. Sent this directly to Taneli, here's the same for > > the list as well: > Please Don't blame you mail client Why not? GMail could recognize the "X-BeenThere: maemo-developers@maemo.org" and "List-*" headers and a) add a reply to list option b) links to the archive, subscribe/unsubscribe options, etc I like GMail for lists because of it's ability to handle volumes of mail and search, sort, and group messages, it's inability to handle standard and common mailing list headers is annoying. I knew I never should have started this disc anyway. sorry about that. If I have to blame somebody I would prefer to blame exchange that discards bulk flags over gmail any day. So, yeah... blame the mail client, and send a suggestion to their development team. Voicing your opinion that "This list is managed backwards and should change" is cool, too, but don't let the mailer get off without a lashing just because you're blaming someone else. Alright, the mail client should make it easy to reply to the mailing list. and Yes I am / was annoyed. Still that does not change my opinion. I am in here for the fun of it and I understand that this is not helping. greetings ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: NPTL support?
On 3/12/07, Kees Jongenburger <[EMAIL PROTECTED]> wrote: On 3/12/07, Lauri Leukkunen <[EMAIL PROTECTED]> wrote: > Bleh, damn gmail.. Sent this directly to Taneli, here's the same for > the list as well: Please Don't blame you mail client Why not? GMail could recognize the "X-BeenThere: maemo-developers@maemo.org" and "List-*" headers and a) add a reply to list option b) links to the archive, subscribe/unsubscribe options, etc I like GMail for lists because of it's ability to handle volumes of mail and search, sort, and group messages, it's inability to handle standard and common mailing list headers is annoying. So, yeah... blame the mail client, and send a suggestion to their development team. Voicing your opinion that "This list is managed backwards and should change" is cool, too, but don't let the mailer get off without a lashing just because you're blaming someone else. --Paul ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: NPTL support?
On 3/12/07, Lauri Leukkunen <[EMAIL PROTECTED]> wrote: Bleh, damn gmail.. Sent this directly to Taneli, here's the same for the list as well: Please Don't blame you mail client Some guys, usually mutt users (also on this list) think this is the way it should work http://www.unicom.com/pw/reply-to-harmful.html This is an ongoing fight. but I have never ever been on a mailing list where people where nagging that the reply was sent to the list.(other than people not being happy that exchange was sending replies to the whole list telling the list the planned holidays and phone numbers where they could be reached). With the current setup this is a real hot topic. Sometimes life is just not fair. greetings ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: NPTL support?
Bleh, damn gmail.. Sent this directly to Taneli, here's the same for the list as well: http://rahina.org/sb2/arm-lltc-gcc412-glibc25.tar.bz2 Not just the glibc, but you can extract it from there. The toolchain itself is built for amd64. /lauri On 3/12/07, Quim Gil <[EMAIL PROTECTED]> wrote: We are going to use glibc 2.5 at some point. This will bring NPTL support. In the meantime... you will need the help of someone more clever than me. :) On Sun, 2007-03-11 at 10:28 +0200, ext T Taneli Vahakangas wrote: > where can I find NPTL-enabled libc (for 770 or N800)? If it isn't > available already, how would I go about making one? -- Quim Gil - http://maemo.org ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: NPTL support?
We are going to use glibc 2.5 at some point. This will bring NPTL support. In the meantime... you will need the help of someone more clever than me. :) On Sun, 2007-03-11 at 10:28 +0200, ext T Taneli Vahakangas wrote: > where can I find NPTL-enabled libc (for 770 or N800)? If it isn't > available already, how would I go about making one? -- Quim Gil - http://maemo.org ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
NPTL support?
(let's retry with a subject line) Hello all, where can I find NPTL-enabled libc (for 770 or N800)? If it isn't available already, how would I go about making one? (I tried google already, but didn't find anything, except that currently only linuxthreads is supported ...) Cheers, Taneli ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
