libposix-development Mailing List for libposix (Page 7)
Status: Pre-Alpha
Brought to you by:
hdante
Menu
▾
▴
libposix-development — This list is for those who develop or are willing to develop libposix
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(16) |
Jun
(122) |
Jul
(49) |
Aug
(19) |
Sep
(6) |
Oct
(4) |
Nov
(1) |
Dec
|
|---|
|
From: Henrique A. <hd...@gm...> - 2009-06-08 15:34:20
|
I moved them because they're really small. The final source has 140 lines. Since they're all mandatory functions we don't need modularity. In general I'll favor easy code browsing over optimization. Source code or directory splits should be done on demand whenever we find that it's necessary. I'm pretty sure llvm LTO can remove isolated functions from the build, for example. See: http://llvm.org/docs/LinkTimeOptimization.html We'll need to optimize for ld anyway at some moment, I can revert the change if you bring me some reference saying that ld (or, say, objcopy) can't do the same. PS: quick googling (concerning ld --gc-sections) suggest the opposite: http://embeddedfreak.wordpress.com/2009/02/10/removing-unused-functionsdead-codes-with-gccgnu-ld/ 2009/6/8 Andreas Krennmair <akr...@go...> > Oh, BTW, I just saw that you moved all the string functions into a single > file. Generally, this is a bad idea. Eventually, libposix will not only have > a shared library version, but also a static library version, and in the > latter case, having each function in a separate source file (and thus in a > separate .o file) brings huge advantages, namely ld can automatically remove > .o files that aren't referenced. On the other hand, having each function > separated into an own file has no real disadvantage in a shared library (the > effects of inter-function optimizations are usually minimal if present at > all), plus having n separate files for n functions usually makes merges > easier than 1 or only a few files that contain everything. > > Regards, > Andreas > > > On Mon, Jun 8, 2009 at 7:48 AM, Andreas Krennmair < > akr...@go...> wrote: > >> If there are differences, you always need an extra merge commit, as far as >> I understand. >> >> >> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote: >> >>> >>> With git pull, I'm not being able to merge each commit individually in >>> my branch: >>> >>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>> Merge: 1faac1a... 05b56ea... >>> Author: Henrique <hd...@us...> >>> Date: Sat Jun 6 17:29:37 2009 -0300 >>> >>> Merge git://github.com/akrennmair/libposix into andreas >>> >>> * git://github.com/akrennmair/libposix: >>> implemented abs(), labs() and llabs() including unit tests. >>> implemented strrchr() including unit tests. >>> fixed build dependencies for tests. >>> added unit tests for already implemented str* functions. >>> added mmap and munmap. >>> added simple unit tests for already implemented mem* functions. >>> >>> Is there a way to fix this ? >>> >>> 2009/6/5 Henrique Almeida <hd...@gm...> >>> >>> >>>> Ok, good idea, git branches rock ! >>>> >>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>> >>>>> Hello everybody, >>>>> >>>>> As the "broken" branch didn't work out as expected, I found a better >>>>> way that both satisfies me in its abilities and also allows other developers >>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>> In this fork, I will regularly keep track of changes in the official >>>>> libposix git repository. But it's also simple to merge my commits into the >>>>> official libposix repository by executing >>>>> git pull git://github.com/akrennmair/libposix.git master >>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>> the place to see and track my changes. Of course, this shall NOT be >>>>> interpreted as a way to get independent from the official project, it is >>>>> merely a way that helps me work in a more flexible fashion on the things >>>>> that I want to work on, plus it makes my changes more visible and also >>>>> easier to reintegrate with the official development line. >>>>> >>>>> Nevertheless, I will continue posting short notifications about the >>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>> some simple functions including unit tests, and I hope to present a simple >>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>> two. >>>>> >>>>> Regards, >>>>> Andreas >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>> looking to deploy the next generation of Solaris that includes the >>>>> latest >>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >>> >>> ------------------------------------------------------------------------------ >>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>> looking to deploy the next generation of Solaris that includes the latest >>> innovations from Sun and the OpenSource community. Download a copy and >>> enjoy capabilities such as Networking, Storage and Virtualization. >>> Go to: http://p.sf.net/sfu/opensolaris-get >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >>> >> > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-08 15:24:39
|
The problem was that the merge was condensed into a single commit (or maybe I didn't notice the other commits in the log). I can try again later, but at the moment there are some merge issues to resolve. 2009/6/8 Andreas Krennmair <akr...@go...> > If there are differences, you always need an extra merge commit, as far as > I understand. > > > On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote: > >> >> With git pull, I'm not being able to merge each commit individually in my >> branch: >> >> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >> Merge: 1faac1a... 05b56ea... >> Author: Henrique <hd...@us...> >> Date: Sat Jun 6 17:29:37 2009 -0300 >> >> Merge git://github.com/akrennmair/libposix into andreas >> >> * git://github.com/akrennmair/libposix: >> implemented abs(), labs() and llabs() including unit tests. >> implemented strrchr() including unit tests. >> fixed build dependencies for tests. >> added unit tests for already implemented str* functions. >> added mmap and munmap. >> added simple unit tests for already implemented mem* functions. >> >> Is there a way to fix this ? >> >> 2009/6/5 Henrique Almeida <hd...@gm...> >> >> >>> Ok, good idea, git branches rock ! >>> >>> 2009/6/5 Andreas Krennmair <akr...@go...> >>> >>>> Hello everybody, >>>> >>>> As the "broken" branch didn't work out as expected, I found a better way >>>> that both satisfies me in its abilities and also allows other developers to >>>> easily see and merge my changes. I have a fork of libposix uploaded on >>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>> In this fork, I will regularly keep track of changes in the official >>>> libposix git repository. But it's also simple to merge my commits into the >>>> official libposix repository by executing >>>> git pull git://github.com/akrennmair/libposix.git master >>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>> the place to see and track my changes. Of course, this shall NOT be >>>> interpreted as a way to get independent from the official project, it is >>>> merely a way that helps me work in a more flexible fashion on the things >>>> that I want to work on, plus it makes my changes more visible and also >>>> easier to reintegrate with the official development line. >>>> >>>> Nevertheless, I will continue posting short notifications about the >>>> things I currently work on to keep everyone informed. So far, I've worked on >>>> some simple functions including unit tests, and I hope to present a simple >>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>> two. >>>> >>>> Regards, >>>> Andreas >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>> looking to deploy the next generation of Solaris that includes the >>>> latest >>>> innovations from Sun and the OpenSource community. Download a copy and >>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> >> ------------------------------------------------------------------------------ >> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >> looking to deploy the next generation of Solaris that includes the latest >> innovations from Sun and the OpenSource community. Download a copy and >> enjoy capabilities such as Networking, Storage and Virtualization. >> Go to: http://p.sf.net/sfu/opensolaris-get >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >> > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-08 07:07:41
|
I wasn't talking about function and data sections, but about .o files only. gcc and binutils support not including unreferenced .o files with .a files for ages (I saw this the first time about 10 years ago). Also, as I said, having one function per file usually makes merging easier. Regards, Andreas On Mon, Jun 8, 2009 at 8:50 AM, Chris Forbes <ch...@fa...>wrote: > I don’t suppose its practical for us to compile a static library version > with –ffunction-sections, -fdata-sections [if using recent gcc] and expect > the library consumer to pass –gc-sections to ld? > > That should get you the size advantages of putting things in their own .o > while not imposing anything on the source layout.. > > > > --Chris > > > > *From:* Andreas Krennmair [mailto:akr...@go...] > *Sent:* Monday, 8 June 2009 5:53 p.m. > *To:* lib...@li... > *Subject:* Re: [libposix-development] My personal development branch > > > > Oh, BTW, I just saw that you moved all the string functions into a single > file. Generally, this is a bad idea. Eventually, libposix will not only have > a shared library version, but also a static library version, and in the > latter case, having each function in a separate source file (and thus in a > separate .o file) brings huge advantages, namely ld can automatically remove > .o files that aren't referenced. On the other hand, having each function > separated into an own file has no real disadvantage in a shared library (the > effects of inter-function optimizations are usually minimal if present at > all), plus having n separate files for n functions usually makes merges > easier than 1 or only a few files that contain everything. > > Regards, > Andreas > > On Mon, Jun 8, 2009 at 7:48 AM, Andreas Krennmair < > akr...@go...> wrote: > > If there are differences, you always need an extra merge commit, as far as > I understand. > > > > On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> > wrote: > > > With git pull, I'm not being able to merge each commit individually in my > branch: > > commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd > Merge: 1faac1a... 05b56ea... > Author: Henrique <hd...@us...> > Date: Sat Jun 6 17:29:37 2009 -0300 > > Merge git://github.com/akrennmair/libposix into andreas > > * git://github.com/akrennmair/libposix: > implemented abs(), labs() and llabs() including unit tests. > implemented strrchr() including unit tests. > fixed build dependencies for tests. > added unit tests for already implemented str* functions. > added mmap and munmap. > added simple unit tests for already implemented mem* functions. > > Is there a way to fix this ? > > 2009/6/5 Henrique Almeida <hd...@gm...> > > > > > Ok, good idea, git branches rock ! > > 2009/6/5 Andreas Krennmair <akr...@go...> > > Hello everybody, > > As the "broken" branch didn't work out as expected, I found a better way > that both satisfies me in its abilities and also allows other developers to > easily see and merge my changes. I have a fork of libposix uploaded on > GitHub: http://github.com/akrennmair/libposix/tree/master > In this fork, I will regularly keep track of changes in the official > libposix git repository. But it's also simple to merge my commits into the > official libposix repository by executing > git pull git://github.com/akrennmair/libposix.git master > in a clone of the official libposix git repository. Anyway, GitHub is the > place to see and track my changes. Of course, this shall NOT be interpreted > as a way to get independent from the official project, it is merely a way > that helps me work in a more flexible fashion on the things that I want to > work on, plus it makes my changes more visible and also easier to > reintegrate with the official development line. > > Nevertheless, I will continue posting short notifications about the things > I currently work on to keep everyone informed. So far, I've worked on some > simple functions including unit tests, and I hope to present a simple > implementation of malloc(), free(), realloc() and calloc() within a day or > two. > > Regards, > Andreas > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > > > > -- > Henrique Dante de Almeida > hd...@gm... > > > > > -- > Henrique Dante de Almeida > hd...@gm... > > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > > > > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > |
|
From: Chris F. <ch...@fa...> - 2009-06-08 06:51:07
|
I don't suppose its practical for us to compile a static library version
with -ffunction-sections, -fdata-sections [if using recent gcc] and
expect the library consumer to pass -gc-sections to ld?
That should get you the size advantages of putting things in their own
.o while not imposing anything on the source layout..
--Chris
From: Andreas Krennmair [mailto:akr...@go...]
Sent: Monday, 8 June 2009 5:53 p.m.
To: lib...@li...
Subject: Re: [libposix-development] My personal development branch
Oh, BTW, I just saw that you moved all the string functions into a
single file. Generally, this is a bad idea. Eventually, libposix will
not only have a shared library version, but also a static library
version, and in the latter case, having each function in a separate
source file (and thus in a separate .o file) brings huge advantages,
namely ld can automatically remove .o files that aren't referenced. On
the other hand, having each function separated into an own file has no
real disadvantage in a shared library (the effects of inter-function
optimizations are usually minimal if present at all), plus having n
separate files for n functions usually makes merges easier than 1 or
only a few files that contain everything.
Regards,
Andreas
On Mon, Jun 8, 2009 at 7:48 AM, Andreas Krennmair
<akr...@go...> wrote:
If there are differences, you always need an extra merge commit, as far
as I understand.
On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
wrote:
With git pull, I'm not being able to merge each commit individually in
my branch:
commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
Merge: 1faac1a... 05b56ea...
Author: Henrique <hd...@us...>
Date: Sat Jun 6 17:29:37 2009 -0300
Merge git://github.com/akrennmair/libposix into andreas
* git://github.com/akrennmair/libposix:
implemented abs(), labs() and llabs() including unit tests.
implemented strrchr() including unit tests.
fixed build dependencies for tests.
added unit tests for already implemented str* functions.
added mmap and munmap.
added simple unit tests for already implemented mem* functions.
Is there a way to fix this ?
2009/6/5 Henrique Almeida <hd...@gm...>
Ok, good idea, git branches rock !
2009/6/5 Andreas Krennmair <akr...@go...>
Hello everybody,
As the "broken" branch didn't work out as expected, I found a
better way that both satisfies me in its abilities and also allows other
developers to easily see and merge my changes. I have a fork of libposix
uploaded on GitHub: http://github.com/akrennmair/libposix/tree/master
In this fork, I will regularly keep track of changes in the
official libposix git repository. But it's also simple to merge my
commits into the official libposix repository by executing
git pull git://github.com/akrennmair/libposix.git master
in a clone of the official libposix git repository. Anyway,
GitHub is the place to see and track my changes. Of course, this shall
NOT be interpreted as a way to get independent from the official
project, it is merely a way that helps me work in a more flexible
fashion on the things that I want to work on, plus it makes my changes
more visible and also easier to reintegrate with the official
development line.
Nevertheless, I will continue posting short notifications about
the things I currently work on to keep everyone informed. So far, I've
worked on some simple functions including unit tests, and I hope to
present a simple implementation of malloc(), free(), realloc() and
calloc() within a day or two.
Regards,
Andreas
------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for
enterprises
looking to deploy the next generation of Solaris that includes
the latest
innovations from Sun and the OpenSource community. Download a
copy and
enjoy capabilities such as Networking, Storage and
Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Libposix-development mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libposix-development
--
Henrique Dante de Almeida
hd...@gm...
--
Henrique Dante de Almeida
hd...@gm...
------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the
latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Libposix-development mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libposix-development
|
|
From: Andreas K. <akr...@go...> - 2009-06-08 05:53:22
|
Oh, BTW, I just saw that you moved all the string functions into a single file. Generally, this is a bad idea. Eventually, libposix will not only have a shared library version, but also a static library version, and in the latter case, having each function in a separate source file (and thus in a separate .o file) brings huge advantages, namely ld can automatically remove .o files that aren't referenced. On the other hand, having each function separated into an own file has no real disadvantage in a shared library (the effects of inter-function optimizations are usually minimal if present at all), plus having n separate files for n functions usually makes merges easier than 1 or only a few files that contain everything. Regards, Andreas On Mon, Jun 8, 2009 at 7:48 AM, Andreas Krennmair <akr...@go... > wrote: > If there are differences, you always need an extra merge commit, as far as > I understand. > > > On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote: > >> >> With git pull, I'm not being able to merge each commit individually in my >> branch: >> >> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >> Merge: 1faac1a... 05b56ea... >> Author: Henrique <hd...@us...> >> Date: Sat Jun 6 17:29:37 2009 -0300 >> >> Merge git://github.com/akrennmair/libposix into andreas >> >> * git://github.com/akrennmair/libposix: >> implemented abs(), labs() and llabs() including unit tests. >> implemented strrchr() including unit tests. >> fixed build dependencies for tests. >> added unit tests for already implemented str* functions. >> added mmap and munmap. >> added simple unit tests for already implemented mem* functions. >> >> Is there a way to fix this ? >> >> 2009/6/5 Henrique Almeida <hd...@gm...> >> >> >>> Ok, good idea, git branches rock ! >>> >>> 2009/6/5 Andreas Krennmair <akr...@go...> >>> >>>> Hello everybody, >>>> >>>> As the "broken" branch didn't work out as expected, I found a better way >>>> that both satisfies me in its abilities and also allows other developers to >>>> easily see and merge my changes. I have a fork of libposix uploaded on >>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>> In this fork, I will regularly keep track of changes in the official >>>> libposix git repository. But it's also simple to merge my commits into the >>>> official libposix repository by executing >>>> git pull git://github.com/akrennmair/libposix.git master >>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>> the place to see and track my changes. Of course, this shall NOT be >>>> interpreted as a way to get independent from the official project, it is >>>> merely a way that helps me work in a more flexible fashion on the things >>>> that I want to work on, plus it makes my changes more visible and also >>>> easier to reintegrate with the official development line. >>>> >>>> Nevertheless, I will continue posting short notifications about the >>>> things I currently work on to keep everyone informed. So far, I've worked on >>>> some simple functions including unit tests, and I hope to present a simple >>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>> two. >>>> >>>> Regards, >>>> Andreas >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>> looking to deploy the next generation of Solaris that includes the >>>> latest >>>> innovations from Sun and the OpenSource community. Download a copy and >>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> >> ------------------------------------------------------------------------------ >> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >> looking to deploy the next generation of Solaris that includes the latest >> innovations from Sun and the OpenSource community. Download a copy and >> enjoy capabilities such as Networking, Storage and Virtualization. >> Go to: http://p.sf.net/sfu/opensolaris-get >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >> > |
|
From: Andreas K. <akr...@go...> - 2009-06-08 05:48:24
|
If there are differences, you always need an extra merge commit, as far as I understand. On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> wrote: > > With git pull, I'm not being able to merge each commit individually in my > branch: > > commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd > Merge: 1faac1a... 05b56ea... > Author: Henrique <hd...@us...> > Date: Sat Jun 6 17:29:37 2009 -0300 > > Merge git://github.com/akrennmair/libposix into andreas > > * git://github.com/akrennmair/libposix: > implemented abs(), labs() and llabs() including unit tests. > implemented strrchr() including unit tests. > fixed build dependencies for tests. > added unit tests for already implemented str* functions. > added mmap and munmap. > added simple unit tests for already implemented mem* functions. > > Is there a way to fix this ? > > 2009/6/5 Henrique Almeida <hd...@gm...> > > >> Ok, good idea, git branches rock ! >> >> 2009/6/5 Andreas Krennmair <akr...@go...> >> >>> Hello everybody, >>> >>> As the "broken" branch didn't work out as expected, I found a better way >>> that both satisfies me in its abilities and also allows other developers to >>> easily see and merge my changes. I have a fork of libposix uploaded on >>> GitHub: http://github.com/akrennmair/libposix/tree/master >>> In this fork, I will regularly keep track of changes in the official >>> libposix git repository. But it's also simple to merge my commits into the >>> official libposix repository by executing >>> git pull git://github.com/akrennmair/libposix.git master >>> in a clone of the official libposix git repository. Anyway, GitHub is the >>> place to see and track my changes. Of course, this shall NOT be interpreted >>> as a way to get independent from the official project, it is merely a way >>> that helps me work in a more flexible fashion on the things that I want to >>> work on, plus it makes my changes more visible and also easier to >>> reintegrate with the official development line. >>> >>> Nevertheless, I will continue posting short notifications about the >>> things I currently work on to keep everyone informed. So far, I've worked on >>> some simple functions including unit tests, and I hope to present a simple >>> implementation of malloc(), free(), realloc() and calloc() within a day or >>> two. >>> >>> Regards, >>> Andreas >>> >>> >>> ------------------------------------------------------------------------------ >>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>> looking to deploy the next generation of Solaris that includes the latest >>> innovations from Sun and the OpenSource community. Download a copy and >>> enjoy capabilities such as Networking, Storage and Virtualization. >>> Go to: http://p.sf.net/sfu/opensolaris-get >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >>> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > |
|
From: Henrique A. <hd...@gm...> - 2009-06-06 20:41:14
|
With git pull, I'm not being able to merge each commit individually in my
branch:
commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
Merge: 1faac1a... 05b56ea...
Author: Henrique <hd...@us...>
Date: Sat Jun 6 17:29:37 2009 -0300
Merge git://github.com/akrennmair/libposix into andreas
* git://github.com/akrennmair/libposix:
implemented abs(), labs() and llabs() including unit tests.
implemented strrchr() including unit tests.
fixed build dependencies for tests.
added unit tests for already implemented str* functions.
added mmap and munmap.
added simple unit tests for already implemented mem* functions.
Is there a way to fix this ?
2009/6/5 Henrique Almeida <hd...@gm...>
>
> Ok, good idea, git branches rock !
>
> 2009/6/5 Andreas Krennmair <akr...@go...>
>
>> Hello everybody,
>>
>> As the "broken" branch didn't work out as expected, I found a better way
>> that both satisfies me in its abilities and also allows other developers to
>> easily see and merge my changes. I have a fork of libposix uploaded on
>> GitHub: http://github.com/akrennmair/libposix/tree/master
>> In this fork, I will regularly keep track of changes in the official
>> libposix git repository. But it's also simple to merge my commits into the
>> official libposix repository by executing
>> git pull git://github.com/akrennmair/libposix.git master
>> in a clone of the official libposix git repository. Anyway, GitHub is the
>> place to see and track my changes. Of course, this shall NOT be interpreted
>> as a way to get independent from the official project, it is merely a way
>> that helps me work in a more flexible fashion on the things that I want to
>> work on, plus it makes my changes more visible and also easier to
>> reintegrate with the official development line.
>>
>> Nevertheless, I will continue posting short notifications about the things
>> I currently work on to keep everyone informed. So far, I've worked on some
>> simple functions including unit tests, and I hope to present a simple
>> implementation of malloc(), free(), realloc() and calloc() within a day or
>> two.
>>
>> Regards,
>> Andreas
>>
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>>
>
>
> --
> Henrique Dante de Almeida
> hd...@gm...
>
--
Henrique Dante de Almeida
hd...@gm...
|
|
From: Henrique A. <hd...@gm...> - 2009-06-06 20:12:42
|
Hello world now supports one more platform: FreeBSD on x86. I think we are done with porting Hello World now. :-) -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-05 16:46:19
|
Hello, people, During the lifetime of the project we'll need many to do many different tasks. This is a list of project roles that may be available. There'll be some roles that you're willing to do and others that you're not. Send me a list of all the project roles that you would be willing to do. Only the "spammer" role should be taken by everyone, since we need to constantly advertise our work. :-P Note that some roles are more urgent now than others. "Performance developer", for example, is useless right now. - C Developer: Will develop ISO C code. One of the main roles of the project. Must have good knowledge of the standard. - Low level developer: Will develop assembly and low level, non necessarily standard code. Must have knowledge of the specific low level tools we're using or targeting (eg: binutils, kernels, architectures) - Tester: Will develop unit tests and port standard applications to our environment, to be used as test cases. Must have great knowledge of the standards. Testers need to become happy whenever they find a bug. - Web designer: Will design the interface of our web pages. Includes the home page, the wiki and other web apps we may use. Should be an artist capable of designing clean websites. - Web developer: Will program the designs made by the web designer. Must be good with CSS, HTML, etc. - Web editor/blogger/"PR guy" etc Will edit and mantain content the website, making announcements and possibly moderating vandalism. Should just be well informed about what's going on in the project. - Build system developer/ports mantainer Will develop code for compiling and installing the library in some set of architectures. Must have knowledge of the build system used, toolchains, cross-compiling, emulators, Unix distros, etc. - Performance developer Will optimize code. Must have knowledge of profiling tools and low level tools/architecture details. - Support/Debugger: Will answer user doubts, track and report bugs and debug or assign them. Must be patient. - Roadmap manager: Will define sub-goals to the project, assign tasks for other project roles, report progress and possibly reevaluate and reorganize goals. Should have experience in management. - Code reviewer: Will review code, specially third party contributions, approve and disapprove them, suggest changes. Will also clean up existing code. Must have good knowledge of the standard and should have experience in writing clean and safe code. - Spammer: Will advertise libposix. Must tell your friends about your project, blog, e-mail, etc. :-P Obviously, I'm willing to take ALL the project roles that prove to be necessary. -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-05 16:44:20
|
Ok, good idea, git branches rock ! 2009/6/5 Andreas Krennmair <akr...@go...> > Hello everybody, > > As the "broken" branch didn't work out as expected, I found a better way > that both satisfies me in its abilities and also allows other developers to > easily see and merge my changes. I have a fork of libposix uploaded on > GitHub: http://github.com/akrennmair/libposix/tree/master > In this fork, I will regularly keep track of changes in the official > libposix git repository. But it's also simple to merge my commits into the > official libposix repository by executing > git pull git://github.com/akrennmair/libposix.git master > in a clone of the official libposix git repository. Anyway, GitHub is the > place to see and track my changes. Of course, this shall NOT be interpreted > as a way to get independent from the official project, it is merely a way > that helps me work in a more flexible fashion on the things that I want to > work on, plus it makes my changes more visible and also easier to > reintegrate with the official development line. > > Nevertheless, I will continue posting short notifications about the things > I currently work on to keep everyone informed. So far, I've worked on some > simple functions including unit tests, and I hope to present a simple > implementation of malloc(), free(), realloc() and calloc() within a day or > two. > > Regards, > Andreas > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-05 16:17:48
|
Hello everybody, As the "broken" branch didn't work out as expected, I found a better way that both satisfies me in its abilities and also allows other developers to easily see and merge my changes. I have a fork of libposix uploaded on GitHub: http://github.com/akrennmair/libposix/tree/master In this fork, I will regularly keep track of changes in the official libposix git repository. But it's also simple to merge my commits into the official libposix repository by executing git pull git://github.com/akrennmair/libposix.git master in a clone of the official libposix git repository. Anyway, GitHub is the place to see and track my changes. Of course, this shall NOT be interpreted as a way to get independent from the official project, it is merely a way that helps me work in a more flexible fashion on the things that I want to work on, plus it makes my changes more visible and also easier to reintegrate with the official development line. Nevertheless, I will continue posting short notifications about the things I currently work on to keep everyone informed. So far, I've worked on some simple functions including unit tests, and I hope to present a simple implementation of malloc(), free(), realloc() and calloc() within a day or two. Regards, Andreas |
|
From: Henrique A. <hd...@gm...> - 2009-06-05 02:30:06
|
Since there are no more comments, let's switch to the 2-clause license. 2009/6/3 Andreas Krennmair <akr...@go...>: > Hi, > > I'm fine with either 2- or 3-clause BSD license. Since 2-clause is pretty > much the standard in the BSD world these days (besides ISC license which is > OpenBSD's preferred license), it's probably wise to stick to it. > > Also an interesting source regarding licenses: > http://www.openbsd.org/policy.html > "The ISC copyright is functionally equivalent to a two-term BSD copyright > with language removed that is made unnecessary by the Berne convention." > > Personally, I'm fine with either of these. > > Regards, > Andreas > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-05 02:15:31
|
2009/6/4 Henrique Almeida <hd...@gm...>: > > I'll backport the changes to x86 today. If there's something blocking > your work, you can warn me and I'll prioritize the solution. Done. > > The "broken" branch is up. > > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-04 17:22:31
|
2009/6/4 Andreas Krennmair <akr...@go...>: > > > > Please the contents of > http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/compat/linux/arch/i386/linux_syscall.h?rev=1.83&content-type=text/x-cvsweb-markup > into system/linux/i386/syscall_nums.h, then that should work. > > > ... which depends on the definition of "working" and "broken". Anyway, good > luck with that, not every developer will have all supported operating > systems on all supported architectures available to check for breakages > prior to a commit. Heck, I don't even have an x86 machine available. I'll backport the changes to x86 today. If there's something blocking your work, you can warn me and I'll prioritize the solution. The "broken" branch is up. > > Regards, > Andreas > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-04 13:26:55
|
Hello everyone, I started with a simple set of unit tests to have some test coverage and an integration into the build system to automatically run tests. So far, only the already implemented mem* routines are covered: http://synflood.at/tmp/libposix/unit-tests-mem.mbox Regards, Andreas |
|
From: Andreas K. <akr...@go...> - 2009-06-04 13:14:47
|
On Thu, Jun 4, 2009 at 2:46 PM, Henrique Almeida <hd...@gm...> wrote: > 2009/6/4 Andreas Krennmair <akr...@go...>: > > Why not, if I may ask? It's not like a broken build suddenly stops git > push > > from working. Or do you always want to have a functioning build in git > > master? > > The current message is: > > gcc -std=c99 -Iinclude -Icompiler/gcc -Iruntime -Wall -Wextra -g > -nostdlib -fPIC -Isystem/linux -Isystem/linux/i386 -c > system/linux/syscalls.c -o output-i386/syscalls.o > system/linux/syscalls.c:30:26: error: syscall_nums.h: Arquivo ou > diretório inexistente > system/linux/syscalls.c: In function ‘write’: > system/linux/syscalls.c:34: error: ‘LINUX_SYS_write’ undeclared (first > use in this function) > system/linux/syscalls.c:34: error: (Each undeclared identifier is > reported only once > system/linux/syscalls.c:34: error: for each function it appears in.) > system/linux/syscalls.c: In function ‘_Exit’: > system/linux/syscalls.c:39: error: ‘LINUX_SYS_exit’ undeclared (first > use in this function) > system/linux/syscalls.c:40: warning: ‘noreturn’ function does return > make: ** [output-i386/syscalls.o] Erro 1 Please the contents of http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/compat/linux/arch/i386/linux_syscall.h?rev=1.83&content-type=text/x-cvsweb-markupinto system/linux/i386/syscall_nums.h, then that should work. > SF repository is for code that always work. Broken commits must stay > in local repositories. ... which depends on the definition of "working" and "broken". Anyway, good luck with that, not every developer will have all supported operating systems on all supported architectures available to check for breakages prior to a commit. Heck, I don't even have an x86 machine available. Regards, Andreas |
|
From: Henrique A. <hd...@gm...> - 2009-06-04 12:53:33
|
2009/6/4 Andreas Krennmair <akr...@go...>: > > > On Thu, Jun 4, 2009 at 12:53 PM, Tordek <ke...@gm...> wrote: >> >> > Or do you always want to have a functioning build in git >> > master? >> >> Seems like the right thing to do. Perhaps we can push an "unstable" >> branch alongside master? > > Only at a certain maturity level, IMHO. Currently I feel it's slowing down > development, especially since Henrique and I seem to be in completely > different timezones. We can have a "broken" branch. I'll add that later. My "official" work hour for libposix is around 0h UTC. I read e-mails frequently, though. > > Regards, > Andreas > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-04 12:52:47
|
2009/6/4 Andreas Krennmair <akr...@go...>: > Why not, if I may ask? It's not like a broken build suddenly stops git push > from working. Or do you always want to have a functioning build in git > master? The current message is: gcc -std=c99 -Iinclude -Icompiler/gcc -Iruntime -Wall -Wextra -g -nostdlib -fPIC -Isystem/linux -Isystem/linux/i386 -c system/linux/syscalls.c -o output-i386/syscalls.o system/linux/syscalls.c:30:26: error: syscall_nums.h: Arquivo ou diretório inexistente system/linux/syscalls.c: In function ‘write’: system/linux/syscalls.c:34: error: ‘LINUX_SYS_write’ undeclared (first use in this function) system/linux/syscalls.c:34: error: (Each undeclared identifier is reported only once system/linux/syscalls.c:34: error: for each function it appears in.) system/linux/syscalls.c: In function ‘_Exit’: system/linux/syscalls.c:39: error: ‘LINUX_SYS_exit’ undeclared (first use in this function) system/linux/syscalls.c:40: warning: ‘noreturn’ function does return make: ** [output-i386/syscalls.o] Erro 1 SF repository is for code that always work. Broken commits must stay in local repositories. > > On Thu, Jun 4, 2009 at 2:11 AM, Henrique Almeida <hd...@gm...> wrote: >> >> I can't, x86 build is broken. >> >> 2009/6/3 Andreas Krennmair <akr...@go...>: >> > On Thu, Jun 4, 2009 at 12:38 AM, Henrique Almeida <hd...@gm...> >> > wrote: >> >> >> >> Applied. >> > >> > Did you do git push? Because I don't see it. >> > >> > Regards, >> > Andreas >> > >> > >> > ------------------------------------------------------------------------------ >> > OpenSolaris 2009.06 is a cutting edge operating system for enterprises >> > looking to deploy the next generation of Solaris that includes the >> > latest >> > innovations from Sun and the OpenSource community. Download a copy and >> > enjoy capabilities such as Networking, Storage and Virtualization. >> > Go to: http://p.sf.net/sfu/opensolaris-get >> > _______________________________________________ >> > Libposix-development mailing list >> > Lib...@li... >> > https://lists.sourceforge.net/lists/listinfo/libposix-development >> > >> > >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> >> ------------------------------------------------------------------------------ >> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >> looking to deploy the next generation of Solaris that includes the latest >> innovations from Sun and the OpenSource community. Download a copy and >> enjoy capabilities such as Networking, Storage and Virtualization. >> Go to: http://p.sf.net/sfu/opensolaris-get >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-04 10:57:09
|
On Thu, Jun 4, 2009 at 12:53 PM, Tordek <ke...@gm...> wrote: > > Or do you always want to have a functioning build in git > > master? > > Seems like the right thing to do. Perhaps we can push an "unstable" > branch alongside master? Only at a certain maturity level, IMHO. Currently I feel it's slowing down development, especially since Henrique and I seem to be in completely different timezones. Regards, Andreas |
|
From: Tordek <ke...@gm...> - 2009-06-04 10:53:16
|
> Or do you always want to have a functioning build in git > master? Seems like the right thing to do. Perhaps we can push an "unstable" branch alongside master? |
|
From: Andreas K. <akr...@go...> - 2009-06-04 08:51:34
|
Why not, if I may ask? It's not like a broken build suddenly stops git push from working. Or do you always want to have a functioning build in git master? On Thu, Jun 4, 2009 at 2:11 AM, Henrique Almeida <hd...@gm...> wrote: > I can't, x86 build is broken. > > 2009/6/3 Andreas Krennmair <akr...@go...>: > > On Thu, Jun 4, 2009 at 12:38 AM, Henrique Almeida <hd...@gm...> > wrote: > >> > >> Applied. > > > > Did you do git push? Because I don't see it. > > > > Regards, > > Andreas > > > > > ------------------------------------------------------------------------------ > > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > > looking to deploy the next generation of Solaris that includes the latest > > innovations from Sun and the OpenSource community. Download a copy and > > enjoy capabilities such as Networking, Storage and Virtualization. > > Go to: http://p.sf.net/sfu/opensolaris-get > > _______________________________________________ > > Libposix-development mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libposix-development > > > > > > > > -- > Henrique Dante de Almeida > hd...@gm... > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > |
|
From: Henrique A. <hd...@gm...> - 2009-06-04 02:46:23
|
We now have a bookshelf: https://apps.sourceforge.net/mediawiki/libposix/index.php?title=Bookshelf All the external documentation we use should be put there. -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-04 01:05:43
|
I've added functions starting with U to the wiki. Let's finish this task. I'll take the remaining functions after wcsncat. Those who have already posted their list, please convert it to the wiki format and update the wiki. 2009/6/2 Henrique Almeida <hd...@gm...>: > I've created the page. See if it can be edited. > > https://apps.sourceforge.net/mediawiki/libposix/index.php?title=Function_list > > 2009/5/31 Henrique Almeida <hd...@gm...>: >> While they don't answer, I was able to put you in the "editor" group. >> >> 2009/5/31 Henrique Almeida <hd...@gm...>: >>> I want to give full access to the wiki, but I have no idea how to do >>> that. I'll send a message to SF. >>> >>> 2009/5/31 David Rocamora <dr...@gm...>: >>>> Henrique, >>>> >>>> Can you open up the permissions on the wiki so I can create a page >>>> called "function list" or what not. I think we should start with the >>>> list we are describing there and have each function link to another >>>> wiki page if more description is needed. The wiki seems locked down >>>> now so I can't add the page myself. >>>> >>>> Thanks, >>>> Dave >>>> >>>> On Thu, May 28, 2009 at 3:23 PM, Henrique Almeida <hd...@gm...> wrote: >>>>> >>>>> >>>>> 2009/5/28 Tordek <ke...@gm...>: >>>>>> Henrique Almeida wrote: >>>>>>> First of all, I hope the message reaches everyone, I'm not sure if >>>>>>> the mailing list is working well, so please reply to this post if >>>>>>> you've received it. >>>>>>> >>>>>> >>>>>> Yes, it is. >>>>> >>>>> Nice. >>>>> >>>>>>> We'll start the project with a simple task. During the project we'll >>>>>>> need to mantain the list with the status of each function in the >>>>>>> project (that is, if it has been implemented, tested, etc.). >>>>>> >>>>>> Do we have a wiki, or another place to post this to? A specific >>>>>> format? (writing the full description of a function as an example >>>>>> would be a great start). >>>>>> >>>>>> I'd strongly reccomend a wiki, to make it highly navigable >>>>>> (categorizing functions per difficulty, and implementedness, for one). >>>>> >>>>> Yes, we definitely need a wiki. SF provides MediaWiki. I have activated it >>>>> on: >>>>> >>>>> http://apps.sourceforge.net/mediawiki/libposix/index.php?title=Main_Page >>>>> >>>>> However, at some moment we'll need to provide a clean and uniform (and >>>>> unique) appearance to the whole site, so we'll need to play with the CSS >>>>> stuff in the wiki. Can you do this ? (btw, we'll need to setup a task >>>>> management page too) >>>>> >>>>> At the moment, the table needs the following >>>>> - function name >>>>> - requirement (mandatory or the option group which it belongs) >>>>> - whether it's obsolescent or not >>>>> - expected difficulty >>>>> >>>>> The table will grow later, but let's keep it simple for now. For the >>>>> functions atoi, crypt and dprintf that would be: >>>>> >>>>> atoi mandatory (not obsolescent) easy >>>>> crypt XSI option (not obsolescent) medium >>>>> dprintf mandatory (not obsolescent) hard >>>>> >>>>> There's another wiki available in SF, called Wikispaces, I don't know if it >>>>> would be better than MediaWiki, though, I've looked at their home page and >>>>> it doesn't seem to be any docs there. >>>>> >>>>>> >>>>>> -- >>>>>> Guillermo O. «Tordek» Freschi. Programador, Escritor, Genio Maligno. >>>>>> http://tordek.com.ar :: http://twitter.com/tordek >>>>>> http://www.arcanopedia.com.ar - Juegos de Rol en Argentina >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT >>>>> is a gathering of tech-side developers & brand creativity professionals. >>>>> Meet >>>>> the minds behind Google Creative Lab, Visual Complexity, Processing, & >>>>> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian >>>>> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>>> >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-04 00:11:18
|
I can't, x86 build is broken. 2009/6/3 Andreas Krennmair <akr...@go...>: > On Thu, Jun 4, 2009 at 12:38 AM, Henrique Almeida <hd...@gm...> wrote: >> >> Applied. > > Did you do git push? Because I don't see it. > > Regards, > Andreas > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-04 00:08:46
|
Hi, On Thu, Jun 4, 2009 at 1:04 AM, Henrique Almeida <hd...@gm...> wrote: > It would be perfect if libposix had a single license. This is > specially important for companies that would like to use libposix. The > 3 clause license seemed okay for me, but both NetBSD and FreeBSD use a > two clause license. The difference is the clause "Neither the name of > the <organization> nor the names of its contributors may be used to > endorse or promote products derived from this software without > specific prior written permission." Since we're not a defined > organization, we could skip that too. We have a few choices: > > - Keep with the 3 clause license. We could define the "libposix > group" just to keep with the "non endorsement" restriction. As long as > we don't actually copy and paste code, I think it's safe to, at least > read other BSD code (I'm not a lawyer, though). :-P > - Change to a 2 clause license. In this case, we can freely copy and > paste NetBSD and FreeBSD code, for example. > - Allow mixing of all BSD-like licenses (that are compatible with GPL > and are not copyleft). Not the ideal world, but no lawyer would die > either. I'm fine with either 2- or 3-clause BSD license. Since 2-clause is pretty much the standard in the BSD world these days (besides ISC license which is OpenBSD's preferred license), it's probably wise to stick to it. Also an interesting source regarding licenses: http://www.openbsd.org/policy.html "The ISC copyright is functionally equivalent to a two-term BSD copyright with language removed that is made unnecessary by the Berne convention." Personally, I'm fine with either of these. Regards, Andreas |
