Thread: [Funk-devel] Building funk
Status: Planning
Brought to you by:
awgh
From: Magnus T. <ma...@th...> - 2007-09-25 07:33:17
Attachments:
src_eggs_Makefile.diff
|
I didn't make it to CCC, again, but looking through the presentation funk stood out as something *really* cool. I just downloaded it from SVN and tried building it. I failed :( Here are some initial observations: - Several files in the SVN repo are automatically generated by autotools. It's generally a bad thing to include those. It's better to assume that people who want to build bleeding edge know how to run 'autoreconf'. - There is a bit of a mixed use of automake and manual make files. It'd probably improve accessibility to do one or the other. - The build fails since recent changes haven't been reflected in the build structure (renaming of raw-sockets and introducing rawsock). I'd be happy to contribute a diff that removes the automatically generated files. I might even find the time to remove the manually written makefiles and replace them with automakefiles. I've attached a small patch for src/eggs/Makefile. Am I correct in my assumptions there? In the meantime please check in the Makefile for rawsock. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus@therning.org Jabber: magnus.therning@gmail.com http://therning.org/magnus C++ is history repeated as tragedy. Java is history repeated as farce. -- Scott McKay |
From: Ben K. <bk...@al...> - 2007-09-25 17:56:56
|
Hello! Unfortunately the SVN is currently in a bad state. Elf has been moving from the original version of the raw-sockets egg to the new-and-improved version. He has assured me that he will be checking in the rest of the new egg sometime today. The new egg will be called 'raw-sockets' as well. What can you do in the meantime? Rather than patching the old raw-sockets, you can always install raw-sockets via the chicken repository. We will only be submitting known-good versions of our eggs to the chicken repository... Try "chicken-setup raw-sockets", it should work. Another, more important topic, is how to keep the SVN from being in a bad state. I have been (and will continue to be) very open with handing out SVN accounts. I would ask everyone with commit to please make sure that the Makefiles still work at a minimum before checking anything in. I will be adding a basic test script in the near future, and will be automating more testing and validation as we go. Thanks much! - Ben Kurtz On 9/24/07, Magnus Therning <ma...@th...> wrote: > > I didn't make it to CCC, again, but looking through the presentation > funk stood out as something *really* cool. > > I just downloaded it from SVN and tried building it. I failed :( > > Here are some initial observations: > > - Several files in the SVN repo are automatically generated by > autotools. It's generally a bad thing to include those. It's better > to assume that people who want to build bleeding edge know how to run > 'autoreconf'. > > - There is a bit of a mixed use of automake and manual make files. > It'd probably improve accessibility to do one or the other. > > - The build fails since recent changes haven't been reflected in the > build structure (renaming of raw-sockets and introducing rawsock). > > I'd be happy to contribute a diff that removes the automatically > generated files. I might even find the time to remove the manually > written makefiles and replace them with automakefiles. > > I've attached a small patch for src/eggs/Makefile. Am I correct in my > assumptions there? > > In the meantime please check in the Makefile for rawsock. > > /M > > -- > Magnus Therning (OpenPGP: 0xAB4DFBA4) > magnus@therning.org Jabber: magnus.therning@gmail.com > http://therning.org/magnus > > C++ is history repeated as tragedy. Java is history repeated as farce. > -- Scott McKay > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Funk-devel mailing list > Fun...@li... > https://lists.sourceforge.net/lists/listinfo/funk-devel > > > |
From: Magnus T. <ma...@th...> - 2007-11-06 13:45:00
Attachments:
funk.patch
|
On Tue, Sep 25, 2007 at 13:56:56 -0400, Ben Kurtz wrote: >Hello! > >Unfortunately the SVN is currently in a bad state. Elf has been moving >from the original version of the raw-sockets egg to the >new-and-improved version. > >He has assured me that he will be checking in the rest of the new egg >sometime today. The new egg will be called 'raw-sockets' as well. > >What can you do in the meantime? > >Rather than patching the old raw-sockets, you can always install >raw-sockets via the chicken repository. We will only be submitting >known-good versions of our eggs to the chicken repository... > >Try "chicken-setup raw-sockets", it should work. > >Another, more important topic, is how to keep the SVN from being in a >bad state. > >I have been (and will continue to be) very open with handing out SVN >accounts. I would ask everyone with commit to please make sure that >the Makefiles still work at a minimum before checking anything in. > >I will be adding a basic test script in the near future, and will be >automating more testing and validation as we go. I've finally found the time to have a second look at funk. Using $CHICKEN_REPOSITORY I managed to install the dependencies without polluting any system directories. Then I put together the patch I've attached. Besides making better use of autoconf/automake this patch also makes funk buildable in a sub-directory. Something that's needed for `make distcheck` to succeed. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus@therning.org Jabber: magnus.therning@gmail.com http://therning.org/magnus |