Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Mike Noyes
On Mon, 2010-09-20 at 02:05 +0300, Andrew wrote: > 20.09.2010 00:17, Mike Noyes пишет: > > Andrew, > > I was referring to LEAF project members. We have over 80. Most of whom, > > aren't code contributers. They help with support, documentation, etc. > > The current access is: > > > > leaf/CVSROOT/av

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Andrew
20.09.2010 00:17, Mike Noyes пишет: > Andrew, > I was referring to LEAF project members. We have over 80. Most of whom, > aren't code contributers. They help with support, documentation, etc. > The current access is: > > leaf/CVSROOT/avail > # Selective access for teams, etc. > avail|arneb, dorus

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Mike Noyes
On Sun, 2010-09-19 at 22:58 +0300, Andrew wrote: > 19.09.2010 21:55, Mike Noyes пишет: > > Andrew, > > Just let me know which developers you want to have access, and I'll > > change it. Alternately, we could make that tree writable by all. Andrew, I was referring to LEAF project members. We have o

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Andrew
19.09.2010 21:55, Mike Noyes пишет: > > Andrew, > Just let me know which developers you want to have access, and I'll > change it. Alternately, we could make that tree writable by all. IMHO it'll not be good if tree will be writable by anyone anonymously or any sourceforge user (if I rightly und

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Mike Noyes
On Sun, 2010-09-19 at 21:12 +0300, Andrew wrote: > 19.09.2010 20:11, davidMbrooke пишет: > > One minor point: when I try building the "root" package it fails at > > building "syslog-ng" because there is no declared dependency on "flex": > > > > cfg-lex.o: In function `yylex': > > cfg-lex.

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Andrew
19.09.2010 20:11, davidMbrooke пишет: > One minor point: when I try building the "root" package it fails at > building "syslog-ng" because there is no declared dependency on "flex": > > cfg-lex.o: In function `yylex': > cfg-lex.c:(.text+0xece): undefined reference to `yywrap' > col

Re: [leaf-devel] Bering-uClibc4: User Documentation: Suggestions for Improvements ?

2010-09-19 Thread davidMbrooke
Thanks Mike, My access is working fine and you will see that I have started creating some pages at https://sourceforge.net/apps/mediawiki/leaf/ Mostly "skeleton" structure (and our logo!) for now but I have some draft content I will copy across when I next get chance. We can use the "discussion"

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread davidMbrooke
On Sun, 2010-09-19 at 16:19 +0300, Andrew wrote: > 19.09.2010 15:59, davidMbrooke пишет: > > > > Sounds good. Let me know when I should try another clean build. > > > > davidMbrooke > > > Try now. I pushed all into CVS, it seems like all will be OK. I'm not > sure about patches of MPFR configure (

Re: [leaf-devel] Bering-uClibc4: User Documentation: Suggestions for Improvements ?

2010-09-19 Thread Mike Noyes
On Sun, 2010-09-19 at 14:53 +0100, davidMbrooke wrote: > Thanks Mike & kp, > > I have been developing some ideas on the documentation structure which I > will upload once I have edit permission to the Wiki. David, Done. The Mediawiki configuration changed a bit. * Davidmbrooke ‎(editor) (C

Re: [leaf-devel] Bering-uClibc4: User Documentation: Suggestions for Improvements ?

2010-09-19 Thread davidMbrooke
Thanks Mike & kp, I have been developing some ideas on the documentation structure which I will upload once I have edit permission to the Wiki. My preference is to keep something similar to the structure we get with the DocBook content (Books, Chapters etc.) and to separate Bering-uClibc 4.x docum

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Andrew
19.09.2010 15:59, davidMbrooke пишет: > > Sounds good. Let me know when I should try another clean build. > > davidMbrooke > Try now. I pushed all into CVS, it seems like all will be OK. I'm not sure about patches of MPFR configure (to avoiding linkage from /lib and /usr/lib) - possible it'll b

Re: [leaf-devel] Bering-uClibc4: User Documentation: Suggestions for Improvements ?

2010-09-19 Thread Mike Noyes
On Fri, 2010-09-17 at 00:24 +0200, KP Kirchdoerfer wrote: > Am Dienstag, 14. September 2010, 21:15:06 schrieb davidMbrooke: -snip- > > We will need some new user (and developer?) documentation for > > Bering-uClibc4, at least to reflect the differences from v3 and > > preferably to improve on what

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread davidMbrooke
Thanks Andrew On Sun, 2010-09-19 at 13:44 +0300, Andrew wrote: > 19.09.2010 00:42, davidMbrooke пишет > > > > The upstream version of elvis is now 2.2 (compared to our current 1.4). > > I use elvis as my main editor on Bering-uClibc so I will look at > > upgrading the package. > > > Yes, it'll be

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Andrew
19.09.2010 15:08, Andrew пишет: >I checked what will be if I just place libraries (gmp, mpfr, mpc) into > GCC dir (as said in http://gcc.gnu.org/install/prerequisites.html) - > this trick doesn't work. So it seems that it's actually needed to > compile these libs twice. Sorry, I read manual i

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Andrew
I checked what will be if I just place libraries (gmp, mpfr, mpc) into GCC dir (as said in http://gcc.gnu.org/install/prerequisites.html) - this trick doesn't work. So it seems that it's actually needed to compile these libs twice. -

Re: [leaf-devel] Bering-uClibc4: Migrating to gcc-4.4.4

2010-09-19 Thread Andrew
19.09.2010 00:42, davidMbrooke пишет: > Hi Andrew, > > The upstream version of elvis is now 2.2 (compared to our current 1.4). > I use elvis as my main editor on Bering-uClibc so I will look at > upgrading the package. > > Our current radius is the Cistron 1.6.8 and a better replacement would > b