Re: [leaf-devel] compiling openswan for BuC4 - update
26.11.2010 12:12, Erich Titl пишет: > > at 26.11.2010 10:15, Andrew wrote: >> 26.11.2010 01:16, Erich Titl пишет: >>> Andrew >>> >>> on 25.11.2010 19:56, Andrew wrote: 25.11.2010 20:45, KP Kirchdoerfer пишет: > Am Freitag, 19. November 2010, 17:18:18 schrieb Erich Titl: >> Hi Folks >> >> I checked the openswan directory into CVS, so everyone can play with it >> now, let me know if you encounter problems with it. >> >> Mike, could you please release the >> src/bering-uclibc4/source/openswan/openswan-2.6.31 directory from CVS, >> as it is not necessary to carry the unpacked source along all the time. >> >> I also added the latest and greatest libgmp, which is needed for >> openswan. >> >> I did not check in my conf/sources.cfg. In my version I commented the >> packages which do not compile and I did not want to foul up the config >> for everyone. If you feel comfortable with commenting or even removing >> the broken targets, please have a look at the diff below. >> >> I have not had time to test the code (yet). If someone has a sandbox to >> run it against, have fun. >> >> cheers >> > Erich, > > if you think libgmp.lrp is required (buildtool.cfg), that means the user > has > to install it, you'll have to package libgmp. > But looking back into Bering-uClibc 3.x package for openswan, it wasn't a > requirement to install libgmp.lrp. > If you need libgmp to _build_ openswan this has to be declared in > sources.cfg > in the "section of the package (as you already did). > > Just for clarification: > build requirements are declared in sources.cfg > additional packages needed to run a package are added in buildtool.cfg > > kp Now we have libgmp in 2 places - one in buildenv package (that is copied into gcc source dir to allow it to be built without libgmp in system), and other - in separate package. Unfortunately, gcc doesn't want to assemble libgmp as shared library. >>> Well, it may not make sense for the compiler to have it shared and it >>> does not even have to be the same release. >>> >>> I looked at the config.log for gcc-final, it specifies that shared >>> libraries should be built. >>> >> If we can force to build libgmp from gcc as shared library in same time >> when we'll build gcc-final - it'll be good. > I guess that should be possible. What is libgmp used for anyway in the > compiler build? Does it just need the header files? > No, gcc needs libgmp present in system, or it can built it if lib is placed in gcc's dir (what we actually done). Maybe we will build libgmp in buildenv separately (specifyong dofferent output dir for building, like we do for gcc) to avoid source duplicates? > All it takes is probably to add a package description for libgmp in > buildtool.cfg for buildenv and call buildpacket.pl at the end of buildenv. > > Then indeed the libgmp package construct is redundant. > > cheers > > Erich No, as I saw gcc doesn't generate libgmp shared library, it looks like gcc is statically linked with it. > > -- > Increase Visibility of Your 3D Game App& Earn a Chance To Win $500! > Tap into the largest installed PC base& get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > > ___ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
at 26.11.2010 10:15, Andrew wrote: > 26.11.2010 01:16, Erich Titl пишет: >> Andrew >> >> on 25.11.2010 19:56, Andrew wrote: >>> 25.11.2010 20:45, KP Kirchdoerfer пишет: Am Freitag, 19. November 2010, 17:18:18 schrieb Erich Titl: > Hi Folks > > I checked the openswan directory into CVS, so everyone can play with it > now, let me know if you encounter problems with it. > > Mike, could you please release the > src/bering-uclibc4/source/openswan/openswan-2.6.31 directory from CVS, > as it is not necessary to carry the unpacked source along all the time. > > I also added the latest and greatest libgmp, which is needed for openswan. > > I did not check in my conf/sources.cfg. In my version I commented the > packages which do not compile and I did not want to foul up the config > for everyone. If you feel comfortable with commenting or even removing > the broken targets, please have a look at the diff below. > > I have not had time to test the code (yet). If someone has a sandbox to > run it against, have fun. > > cheers > Erich, if you think libgmp.lrp is required (buildtool.cfg), that means the user has to install it, you'll have to package libgmp. But looking back into Bering-uClibc 3.x package for openswan, it wasn't a requirement to install libgmp.lrp. If you need libgmp to _build_ openswan this has to be declared in sources.cfg in the " section of the package (as you already did). Just for clarification: build requirements are declared in sources.cfg additional packages needed to run a package are added in buildtool.cfg kp >>> Now we have libgmp in 2 places - one in buildenv package (that is copied >>> into gcc source dir to allow it to be built without libgmp in system), >>> and other - in separate package. Unfortunately, gcc doesn't want to >>> assemble libgmp as shared library. >> Well, it may not make sense for the compiler to have it shared and it >> does not even have to be the same release. >> >> I looked at the config.log for gcc-final, it specifies that shared >> libraries should be built. >> > If we can force to build libgmp from gcc as shared library in same time > when we'll build gcc-final - it'll be good. I guess that should be possible. What is libgmp used for anyway in the compiler build? Does it just need the header files? >>> Maybe we will build libgmp in buildenv separately (specifyong dofferent >>> output dir for building, like we do for gcc) to avoid source duplicates? All it takes is probably to add a package description for libgmp in buildtool.cfg for buildenv and call buildpacket.pl at the end of buildenv. Then indeed the libgmp package construct is redundant. cheers Erich -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
26.11.2010 01:16, Erich Titl пишет: > Andrew > > on 25.11.2010 19:56, Andrew wrote: >> 25.11.2010 20:45, KP Kirchdoerfer пишет: >>> Am Freitag, 19. November 2010, 17:18:18 schrieb Erich Titl: Hi Folks I checked the openswan directory into CVS, so everyone can play with it now, let me know if you encounter problems with it. Mike, could you please release the src/bering-uclibc4/source/openswan/openswan-2.6.31 directory from CVS, as it is not necessary to carry the unpacked source along all the time. I also added the latest and greatest libgmp, which is needed for openswan. I did not check in my conf/sources.cfg. In my version I commented the packages which do not compile and I did not want to foul up the config for everyone. If you feel comfortable with commenting or even removing the broken targets, please have a look at the diff below. I have not had time to test the code (yet). If someone has a sandbox to run it against, have fun. cheers >>> Erich, >>> >>> if you think libgmp.lrp is required (buildtool.cfg), that means the user has >>> to install it, you'll have to package libgmp. >>> But looking back into Bering-uClibc 3.x package for openswan, it wasn't a >>> requirement to install libgmp.lrp. >>> If you need libgmp to _build_ openswan this has to be declared in >>> sources.cfg >>> in the " section of the package (as you already did). >>> >>> Just for clarification: >>> build requirements are declared in sources.cfg >>> additional packages needed to run a package are added in buildtool.cfg >>> >>> kp >> Now we have libgmp in 2 places - one in buildenv package (that is copied >> into gcc source dir to allow it to be built without libgmp in system), >> and other - in separate package. Unfortunately, gcc doesn't want to >> assemble libgmp as shared library. > Well, it may not make sense for the compiler to have it shared and it > does not even have to be the same release. > > I looked at the config.log for gcc-final, it specifies that shared > libraries should be built. > If we can force to build libgmp from gcc as shared library in same time when we'll build gcc-final - it'll be good. >> Maybe we will build libgmp in buildenv separately (specifyong dofferent >> output dir for building, like we do for gcc) to avoid source duplicates? > Which gmp version is used for the compiler? > > Erich I used latest library that was available when I updated gcc. Of course it can be replaced by newer. -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
on 26.11.2010 00:31, KP Kirchdoerfer wrote: > Am Freitag, 26. November 2010, 00:16:17 schrieb Erich Titl: >> Andrew >> >> on 25.11.2010 19:56, Andrew wrote: >>> 25.11.2010 20:45, KP Kirchdoerfer пишет: Am Freitag, 19. November 2010, 17:18:18 schrieb Erich Titl: > Hi Folks > > I checked the openswan directory into CVS, so everyone can play with it > now, let me know if you encounter problems with it. > > Mike, could you please release the > src/bering-uclibc4/source/openswan/openswan-2.6.31 directory from CVS, > as it is not necessary to carry the unpacked source along all the time. > > I also added the latest and greatest libgmp, which is needed for > openswan. > > I did not check in my conf/sources.cfg. In my version I commented the > packages which do not compile and I did not want to foul up the config > for everyone. If you feel comfortable with commenting or even removing > the broken targets, please have a look at the diff below. > > I have not had time to test the code (yet). If someone has a sandbox to > run it against, have fun. > > cheers Erich, if you think libgmp.lrp is required (buildtool.cfg), that means the user has to install it, you'll have to package libgmp. But looking back into Bering-uClibc 3.x package for openswan, it wasn't a requirement to install libgmp.lrp. If you need libgmp to _build_ openswan this has to be declared in sources.cfg in the " section of the package (as you already did). Just for clarification: build requirements are declared in sources.cfg additional packages needed to run a package are added in buildtool.cfg kp >>> >>> Now we have libgmp in 2 places - one in buildenv package (that is copied >>> into gcc source dir to allow it to be built without libgmp in system), >>> and other - in separate package. Unfortunately, gcc doesn't want to >>> assemble libgmp as shared library. >> >> Well, it may not make sense for the compiler to have it shared and it >> does not even have to be the same release. >> >> I looked at the config.log for gcc-final, it specifies that shared >> libraries should be built. >> >>> Maybe we will build libgmp in buildenv separately (specifyong dofferent >>> output dir for building, like we do for gcc) to avoid source duplicates? >> >> Which gmp version is used for the compiler? > > grep gmp source/buildenv/buildtool.cfg > # gmp > Mhhh... not really recent cheers Erich -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
Am Freitag, 26. November 2010, 00:16:17 schrieb Erich Titl: > Andrew > > on 25.11.2010 19:56, Andrew wrote: > > 25.11.2010 20:45, KP Kirchdoerfer пишет: > >> Am Freitag, 19. November 2010, 17:18:18 schrieb Erich Titl: > >>> Hi Folks > >>> > >>> I checked the openswan directory into CVS, so everyone can play with it > >>> now, let me know if you encounter problems with it. > >>> > >>> Mike, could you please release the > >>> src/bering-uclibc4/source/openswan/openswan-2.6.31 directory from CVS, > >>> as it is not necessary to carry the unpacked source along all the time. > >>> > >>> I also added the latest and greatest libgmp, which is needed for > >>> openswan. > >>> > >>> I did not check in my conf/sources.cfg. In my version I commented the > >>> packages which do not compile and I did not want to foul up the config > >>> for everyone. If you feel comfortable with commenting or even removing > >>> the broken targets, please have a look at the diff below. > >>> > >>> I have not had time to test the code (yet). If someone has a sandbox to > >>> run it against, have fun. > >>> > >>> cheers > >> > >> Erich, > >> > >> if you think libgmp.lrp is required (buildtool.cfg), that means the user > >> has to install it, you'll have to package libgmp. > >> But looking back into Bering-uClibc 3.x package for openswan, it wasn't > >> a requirement to install libgmp.lrp. > >> If you need libgmp to _build_ openswan this has to be declared in > >> sources.cfg in the " section of the package (as you already > >> did). > >> > >> Just for clarification: > >> build requirements are declared in sources.cfg > >> additional packages needed to run a package are added in buildtool.cfg > >> > >> kp > > > > Now we have libgmp in 2 places - one in buildenv package (that is copied > > into gcc source dir to allow it to be built without libgmp in system), > > and other - in separate package. Unfortunately, gcc doesn't want to > > assemble libgmp as shared library. > > Well, it may not make sense for the compiler to have it shared and it > does not even have to be the same release. > > I looked at the config.log for gcc-final, it specifies that shared > libraries should be built. > > > Maybe we will build libgmp in buildenv separately (specifyong dofferent > > output dir for building, like we do for gcc) to avoid source duplicates? > > Which gmp version is used for the compiler? grep gmp source/buildenv/buildtool.cfg # gmp Directory = gmp # gmp kp -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
Andrew on 25.11.2010 19:56, Andrew wrote: > 25.11.2010 20:45, KP Kirchdoerfer пишет: >> Am Freitag, 19. November 2010, 17:18:18 schrieb Erich Titl: >>> Hi Folks >>> >>> I checked the openswan directory into CVS, so everyone can play with it >>> now, let me know if you encounter problems with it. >>> >>> Mike, could you please release the >>> src/bering-uclibc4/source/openswan/openswan-2.6.31 directory from CVS, >>> as it is not necessary to carry the unpacked source along all the time. >>> >>> I also added the latest and greatest libgmp, which is needed for openswan. >>> >>> I did not check in my conf/sources.cfg. In my version I commented the >>> packages which do not compile and I did not want to foul up the config >>> for everyone. If you feel comfortable with commenting or even removing >>> the broken targets, please have a look at the diff below. >>> >>> I have not had time to test the code (yet). If someone has a sandbox to >>> run it against, have fun. >>> >>> cheers >>> >> Erich, >> >> if you think libgmp.lrp is required (buildtool.cfg), that means the user has >> to install it, you'll have to package libgmp. >> But looking back into Bering-uClibc 3.x package for openswan, it wasn't a >> requirement to install libgmp.lrp. >> If you need libgmp to _build_ openswan this has to be declared in >> sources.cfg >> in the " section of the package (as you already did). >> >> Just for clarification: >> build requirements are declared in sources.cfg >> additional packages needed to run a package are added in buildtool.cfg >> >> kp > Now we have libgmp in 2 places - one in buildenv package (that is copied > into gcc source dir to allow it to be built without libgmp in system), > and other - in separate package. Unfortunately, gcc doesn't want to > assemble libgmp as shared library. Well, it may not make sense for the compiler to have it shared and it does not even have to be the same release. I looked at the config.log for gcc-final, it specifies that shared libraries should be built. > Maybe we will build libgmp in buildenv separately (specifyong dofferent > output dir for building, like we do for gcc) to avoid source duplicates? Which gmp version is used for the compiler? Erich -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
25.11.2010 20:45, KP Kirchdoerfer пишет: > Am Freitag, 19. November 2010, 17:18:18 schrieb Erich Titl: >> Hi Folks >> >> I checked the openswan directory into CVS, so everyone can play with it >> now, let me know if you encounter problems with it. >> >> Mike, could you please release the >> src/bering-uclibc4/source/openswan/openswan-2.6.31 directory from CVS, >> as it is not necessary to carry the unpacked source along all the time. >> >> I also added the latest and greatest libgmp, which is needed for openswan. >> >> I did not check in my conf/sources.cfg. In my version I commented the >> packages which do not compile and I did not want to foul up the config >> for everyone. If you feel comfortable with commenting or even removing >> the broken targets, please have a look at the diff below. >> >> I have not had time to test the code (yet). If someone has a sandbox to >> run it against, have fun. >> >> cheers >> > Erich, > > if you think libgmp.lrp is required (buildtool.cfg), that means the user has > to install it, you'll have to package libgmp. > But looking back into Bering-uClibc 3.x package for openswan, it wasn't a > requirement to install libgmp.lrp. > If you need libgmp to _build_ openswan this has to be declared in sources.cfg > in the " section of the package (as you already did). > > Just for clarification: > build requirements are declared in sources.cfg > additional packages needed to run a package are added in buildtool.cfg > > kp Now we have libgmp in 2 places - one in buildenv package (that is copied into gcc source dir to allow it to be built without libgmp in system), and other - in separate package. Unfortunately, gcc doesn't want to assemble libgmp as shared library. Maybe we will build libgmp in buildenv separately (specifyong dofferent output dir for building, like we do for gcc) to avoid source duplicates? -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
Am Freitag, 19. November 2010, 17:18:18 schrieb Erich Titl: > Hi Folks > > I checked the openswan directory into CVS, so everyone can play with it > now, let me know if you encounter problems with it. > > Mike, could you please release the > src/bering-uclibc4/source/openswan/openswan-2.6.31 directory from CVS, > as it is not necessary to carry the unpacked source along all the time. > > I also added the latest and greatest libgmp, which is needed for openswan. > > I did not check in my conf/sources.cfg. In my version I commented the > packages which do not compile and I did not want to foul up the config > for everyone. If you feel comfortable with commenting or even removing > the broken targets, please have a look at the diff below. > > I have not had time to test the code (yet). If someone has a sandbox to > run it against, have fun. > > cheers > Erich, if you think libgmp.lrp is required (buildtool.cfg), that means the user has to install it, you'll have to package libgmp. But looking back into Bering-uClibc 3.x package for openswan, it wasn't a requirement to install libgmp.lrp. If you need libgmp to _build_ openswan this has to be declared in sources.cfg in the " section of the package (as you already did). Just for clarification: build requirements are declared in sources.cfg additional packages needed to run a package are added in buildtool.cfg kp -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] compiling openswan for BuC4 - update
Hi Folks I checked the openswan directory into CVS, so everyone can play with it now, let me know if you encounter problems with it. Mike, could you please release the src/bering-uclibc4/source/openswan/openswan-2.6.31 directory from CVS, as it is not necessary to carry the unpacked source along all the time. I also added the latest and greatest libgmp, which is needed for openswan. I did not check in my conf/sources.cfg. In my version I commented the packages which do not compile and I did not want to foul up the config for everyone. If you feel comfortable with commenting or even removing the broken targets, please have a look at the diff below. I have not had time to test the code (yet). If someone has a sandbox to run it against, have fun. cheers Erich Index: sources.cfg === RCS file: /cvsroot/leaf/src/bering-uclibc4/buildtool/conf/sources.cfg,v retrieving revision 1.77 diff -r1.77 sources.cfg 12,16c12,16 < < Type = viewcvs < Name = leaf.cvs.sourceforge.net < Serverpath = /leaf/src/bering-uclibc4/source < --- > # > # Type = viewcvs > # Name = leaf.cvs.sourceforge.net > # Serverpath = /leaf/src/bering-uclibc4/source > # 49,52c49,53 < # < # Type = file < # Serverpath = /PATH/TO/src/bering-uclibc/apps < # --- > > Type = file > Serverpath = /home/mega/leaf/bering-uclibc/devel/src/bering-uclibc4/source > > 1048,1058c1049,1059 < < Server = cvs4-sourceforge < Revision = HEAD < Directory = lcd4linux < Description = LCD support for LEAF < < Name = autoconf < Name = automake < Name = buildenv < < --- > # > # Server = cvs4-sourceforge > # Revision = HEAD > # Directory = lcd4linux > # Description = LCD support for LEAF > # > # Name = autoconf > # Name = automake > # Name = buildenv > # > # 1554,1563c1555,1564 < < Server = cvs-sourceforge < Directory = wlan-ng < revision = HEAD < Description = wlan-ng < < Name = buildenv < Name = kernel < < --- > # > # Server = cvs-sourceforge > # Directory = wlan-ng > # revision = HEAD > # Description = wlan-ng > # > # Name = buildenv > # Name = kernel > # > # 1634,1644c1635,1645 < < Server = cvs-sourceforge < Revision = HEAD < Directory = isdn < Description = ISDN support < < Name = autoconf < Name = automake < Name = buildenv < < --- > # > # Server = cvs-sourceforge > # Revision = HEAD > # Directory = isdn > # Description = ISDN support > # > # Name = autoconf > # Name = automake > # Name = buildenv > # > # 1749,1757c1750,1758 < # < #Server = cvs-sourceforge < #Revision = HEAD < #Directory = libgmp3 < #Description = Multiprecision arithmetic library < # < #Name = buildenv < # < # --- > > Server = cvs4-sourceforge > Revision = HEAD > Directory = libgmp > Description = Multiprecision arithmetic library > > Name = buildenv > > 1860c1861 < Server = cvs-sourceforge --- > Server = cvs4-sourceforge 1866a1868 > Name = libgmp 1913c1915 < Server = cvs-sourceforge --- > Server = cvs4-sourceforge 1952,1961c1954,1963 < < Server = cvs-sourceforge < Directory = fritz < revision = HEAD < Description = CAPI drivers for Fritz!PCI 2.0 < < Name = buildenv < Name = isdn < < --- > # > # Server = cvs-sourceforge > # Directory = fritz > # revision = HEAD > # Description = CAPI drivers for Fritz!PCI 2.0 > # > # Name = buildenv > # Name = isdn > # > # 1963,1972c1965,1974 < < Server = cvs-contrib-sourceforge < Revision = HEAD < Directory = unicorn < Description = Unicorn driver for BeWAN USB/PCI ADSL cards < < Name = buildenv < Name = kernel < < --- > # > # Server = cvs-contrib-sourceforge > # Revision = HEAD > # Directory = unicorn > # Description = Unicorn driver for BeWAN USB/PCI ADSL cards > # > # Name = buildenv > # Name = kernel > # > # 2006,2016c2008,2018 < < Server = cvs-contrib-sourceforge < Directory = lirc < revision = HEAD < Description = Linux Infra Red Controller < < Name = buildenv < Name = kernel < Name = libusb < < --- > # > # Server = cvs-contrib-sourceforge > # Directory = lirc > # revision = HEAD > # Description = Linux Infra Red Controller > # >
Re: [leaf-devel] compiling openswan for BuC4 - update
On Thu, 2010-11-18 at 22:13 +0100, Erich Titl wrote: > Hi Mike > > on 18.11.2010 14:41, Mike Noyes wrote: > > On Thu, 2010-11-18 at 12:05 +0200, Andrew wrote: > >> Yes, of course, we decided earlier that anybody who wants to fix > >> package/improve something will get write access to CVS tree. > > > > Andrew, > > Done. > > > > Erich, > > You now have write access. > > > > Thanks, I will do some more testing and integration before committing. > Sorry :-) > > BTW. does someone know why my messages never make it to leaf-devel if > they are signed? Erich, It is due to our spam filters in mailman. I can look at the situation to see if something can be done. I apologize for any inconvenience this issue has caused you. -- Mike Noyes http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
Hi Mike on 18.11.2010 14:41, Mike Noyes wrote: > On Thu, 2010-11-18 at 12:05 +0200, Andrew wrote: >> Yes, of course, we decided earlier that anybody who wants to fix >> package/improve something will get write access to CVS tree. > > Andrew, > Done. > > Erich, > You now have write access. > Thanks, I will do some more testing and integration before committing. Sorry :-) BTW. does someone know why my messages never make it to leaf-devel if they are signed? cheers Erich -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
On Thu, 2010-11-18 at 12:05 +0200, Andrew wrote: > Yes, of course, we decided earlier that anybody who wants to fix > package/improve something will get write access to CVS tree. Andrew, Done. Erich, You now have write access. -- Mike Noyes http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
17.11.2010 20:43, Mike Noyes пишет: > On Wed, 2010-11-17 at 20:05 +0200, Andrew wrote: >> 17.11.2010 19:51, Erich Titl пишет: >>> Hi Folks >>> >>> Indeed setting >>> >>> UCLIBC_HAS_GNU_GLOB=y >>> >>> in the buildenv makes the compile error for openswan go away. I would >>> like to suggest to include this in the main trunk. >>> >>> cheers >>> >>> Erich >> Yes, of course. You have write access for v4 tree? > Andrew, > Not yet. See below: > > Forwarded Message > From: Mike Noyes > Reply-to: Mike Noyes > To: leaf-devel@lists.sourceforge.net > Subject: Re: [leaf-devel] trying to get to BuC4 > Date: Sun, 14 Nov 2010 07:53:28 -0800 > > On Sun, 2010-11-14 at 13:53 +0100, Erich Titl wrote: >> on 14.11.2010 12:34, davidMbrooke wrote: >>> The WRAP boards are a key target platform for BuC 4.x. However, I do not >>> have one so personally I cannot test compatibility. >> I will port the wd1100 code again. What is the current canonical form of >> entering it into the mainline? Still a patch against the kernel? > Andrew& KP, > I move that Erich receive write access to BuC 4.x in CVS. > > CVSROOT/avail > avail|arneb, dorus, espakman, hejl, hun, lfcorreia, nangel, nitr0man, > davidmbrooke|src/bering-uclibc4 > Yes, of course, we decided earlier that anybody who wants to fix package/improve something will get write access to CVS tree. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
On Wed, 2010-11-17 at 20:05 +0200, Andrew wrote: > 17.11.2010 19:51, Erich Titl пишет: > > Hi Folks > > > > Indeed setting > > > > UCLIBC_HAS_GNU_GLOB=y > > > > in the buildenv makes the compile error for openswan go away. I would > > like to suggest to include this in the main trunk. > > > > cheers > > > > Erich > Yes, of course. You have write access for v4 tree? Andrew, Not yet. See below: Forwarded Message From: Mike Noyes Reply-to: Mike Noyes To: leaf-devel@lists.sourceforge.net Subject: Re: [leaf-devel] trying to get to BuC4 Date: Sun, 14 Nov 2010 07:53:28 -0800 On Sun, 2010-11-14 at 13:53 +0100, Erich Titl wrote: > on 14.11.2010 12:34, davidMbrooke wrote: > > The WRAP boards are a key target platform for BuC 4.x. However, I do not > > have one so personally I cannot test compatibility. > > I will port the wd1100 code again. What is the current canonical form of > entering it into the mainline? Still a patch against the kernel? Andrew & KP, I move that Erich receive write access to BuC 4.x in CVS. CVSROOT/avail avail|arneb, dorus, espakman, hejl, hun, lfcorreia, nangel, nitr0man, davidmbrooke|src/bering-uclibc4 -- Mike Noyes http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, sourceforge/sitedocs -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
17.11.2010 19:51, Erich Titl пишет: > Hi Folks > > Indeed setting > > UCLIBC_HAS_GNU_GLOB=y > > in the buildenv makes the compile error for openswan go away. I would > like to suggest to include this in the main trunk. > > cheers > > Erich Yes, of course. You have write access for v4 tree? -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling openswan for BuC4 - update
Hi Folks Indeed setting UCLIBC_HAS_GNU_GLOB=y in the buildenv makes the compile error for openswan go away. I would like to suggest to include this in the main trunk. cheers Erich -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
