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 "<Requires> 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
