libposix-development Mailing List for libposix (Page 2)
Status: Pre-Alpha
Brought to you by:
hdante
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-08-01 14:22:06
|
In x86_32, there are two mmap system calls. The newest one is defined as LINUX_SYS_mmap2, ie, there's is a "2" in the name. The two system_call_numbers.h are a mess and should be fixed anyway. 2009/8/1 John Haitas <jh...@gm...>: > why is mmap defined in system/linux/x86_32/system_call_numbers.h but > not system/linux/x86_64/system_call_numbers.h ? > > -- > John Haitas > jh...@gm... > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... |
From: John H. <jh...@gm...> - 2009-08-01 06:44:22
|
why is mmap defined in system/linux/x86_32/system_call_numbers.h but not system/linux/x86_64/system_call_numbers.h ? -- John Haitas jh...@gm... |
From: John H. <jh...@gm...> - 2009-08-01 06:35:00
|
it seems as if mmap isn't defined for 64bit /home/jhaitas/src/libposix-git/system/linux/system_calls.c: In function ‘mmap’: /home/jhaitas/src/libposix-git/system/linux/system_calls.c:62: error: ‘LINUX_SYS_mmap2’ undeclared (first use in this function) /home/jhaitas/src/libposix-git/system/linux/system_calls.c:62: error: (Each undeclared identifier is reported only once /home/jhaitas/src/libposix-git/system/linux/system_calls.c:62: error: for each function it appears in.) /home/jhaitas/src/libposix-git/system/linux/system_calls.c:63: warning: cast to pointer from integer of different size /home/jhaitas/src/libposix-git/system/linux/system_calls.c:63: warning: cast to pointer from integer of different size /home/jhaitas/src/libposix-git/system/linux/system_calls.c:64: warning: cast to pointer from integer of different size /home/jhaitas/src/libposix-git/system/linux/system_calls.c: In function ‘system_open’: /home/jhaitas/src/libposix-git/system/linux/system_calls.c:75: warning: cast to pointer from integer of different size /home/jhaitas/src/libposix-git/system/linux/system_calls.c:76: warning: cast to pointer from integer of different size On Sat, Aug 1, 2009 at 1:15 AM, <jh...@gm...> wrote: > its not building on 64bit linux... > > [ 55%] Building C object CMakeFiles/posix.dir/mandatory/printf_scanner.c.o > [ 58%] Building C object CMakeFiles/posix.dir/system/linux/system_calls.c.o > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c: > In function ‘write’: > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:38: > warning: cast to pointer from integer of different size > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c: > In function ‘_Exit’: > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:44: > warning: cast to pointer from integer of different size > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c: > In function ‘mmap’: > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:62: > error: ‘LINUX_SYS_mmap2’ undeclared (first use in this function) > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:62: > error: (Each undeclared identifier is reported only once > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:62: > error: for each function it appears in.) > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:63: > warning: cast to pointer from integer of different size > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:63: > warning: cast to pointer from integer of different size > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:64: > warning: cast to pointer from integer of different size > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c: > In function ‘system_open’: > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:75: > warning: cast to pointer from integer of different size > /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:76: > warning: cast to pointer from integer of different size > make[3]: *** [CMakeFiles/posix.dir/system/linux/system_calls.c.o] Error 1 > make[3]: Leaving directory > `/home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5' > make[2]: *** [CMakeFiles/posix.dir/all] Error 2 > make[2]: Leaving directory > `/home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5' > make[1]: *** [all] Error 2 > make[1]: Leaving directory > `/home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5' > make: *** [build] Error 2 > dpkg-buildpackage: failure: debian/rules build gave error exit status 2 > bzr: ERROR: The build failed. > > > On Fri, Jul 31, 2009 at 9:00 PM, Henrique Almeida<hd...@gm...> wrote: >> >> I've fixed the compilation for x86 and included mmap (I've changed >> the sbrk call to mmap). I don't know yet if it compiles under other >> platforms and I haven't tested on any platform, so expect crashes. >> >> 2009/7/31 <jh...@gm...>: >>> >>> The current HEAD doesn't build... My fault... >>> >>> >>> On Fri, Jul 31, 2009 at 3:24 PM, <jh...@gm...> wrote: >>>> >>>> There is one error. Search for sbrk >>>> >>>> On Fri, Jul 31, 2009 at 2:10 PM, Henrique Almeida<hd...@gm...> >>>> wrote: >>>>> >>>>> Yes, that would be a good start. >>>>> >>>>> 2009/7/31 <jh...@gm...>: >>>>>> >>>>>> I could get us started by implementing the version of malloc taught in >>>>>> K&R >>>>>> C. >>>>>> >>>>>> Just an thought... >>>>>> >>>>>> On Fri, Jul 31, 2009 at 11:29 AM, Henrique Almeida<hd...@gm...> >>>>>> wrote: >>>>>>> >>>>>>> I've spent too much time studying dlmalloc and there are still many >>>>>>> details that I don't understand. I'm considering trying alternative >>>>>>> implementations. >>>>>>> >>>>>>> 2009/7/22 Henrique Almeida <hd...@gm...>: >>>>>>>> >>>>>>>> I'm thinking about reimplementing Doug Lea's malloc for libposix, >>>>>>>> at >>>>>>>> least while we don't have threading support. I'm currently studying >>>>>>>> his implementation. malloc is an important function that we're >>>>>>>> missing. >>>>>>>> >>>>>>>> 2009/7/16 Henrique Almeida <hd...@gm...>: >>>>>>>>> >>>>>>>>> 2009/7/16 Chris Forbes <ch...@fa...>: >>>>>>>>>> >>>>>>>>>> I think I've finally got git figured out (unwiring my brain from >>>>>>>>>> using >>>>>>>>>> SVN :(), >>>>>>>>>> so I'll do some of the other functions for bzip2 after work. >>>>>>>>> >>>>>>>>> I have to write a git howto for the project, but I won't have time >>>>>>>>> in >>>>>>>>> the next weeks. The task is at TaskFreak site. Basically, git has >>>>>>>>> two >>>>>>>>> main differences from svn (that make things look complicated), >>>>>>>>> which >>>>>>>>> are multiple repositories (as a natural part of the development) >>>>>>>>> and >>>>>>>>> somewhat different terminology. So, to work with git you first need >>>>>>>>> to >>>>>>>>> recreate your own repository. Then you'll work by commiting >>>>>>>>> frequently >>>>>>>>> to your local repository. When the code is in a usable state for >>>>>>>>> everyone, you merge your repository with SF repository. The >>>>>>>>> commands >>>>>>>>> are the following: >>>>>>>>> >>>>>>>>> # Create a full local clone of the remote repository (and setup >>>>>>>>> remote >>>>>>>>> merges) >>>>>>>>> git clone >>>>>>>>> ssh://hd...@li.../gitroot/libposix >>>>>>>>> >>>>>>>>> # Merge the remote repository in your local repository >>>>>>>>> git pull >>>>>>>>> >>>>>>>>> # Merge the remote repository (other than SF) in your local >>>>>>>>> repository >>>>>>>>> git pull http://remote.repository.com/ >>>>>>>>> >>>>>>>>> # Edit code >>>>>>>>> editor source1 source2 source3 (git is not used) >>>>>>>>> >>>>>>>>> # View list of changed files >>>>>>>>> git status >>>>>>>>> >>>>>>>>> # View code changes >>>>>>>>> git diff >>>>>>>>> >>>>>>>>> # Add files to commit >>>>>>>>> git add source1/dir1 >>>>>>>>> >>>>>>>>> # Remove files >>>>>>>>> git rm source1 >>>>>>>>> >>>>>>>>> # Move files >>>>>>>>> git mv source1 dest1 >>>>>>>>> >>>>>>>>> # View code changes that were marked as added to commit (with git >>>>>>>>> add) >>>>>>>>> git diff HEAD >>>>>>>>> >>>>>>>>> # Commit (to the local repository) >>>>>>>>> git commit >>>>>>>>> >>>>>>>>> # View the commit log >>>>>>>>> git log >>>>>>>>> >>>>>>>>> # Merge the local repository to the remote repository (upload code >>>>>>>>> to >>>>>>>>> SF) >>>>>>>>> git push >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- Chris >>>>>>>>>> >>>>>>>>>> -----Original Message----- >>>>>>>>>> From: Henrique Almeida [mailto:hd...@gm...] >>>>>>>>>> Sent: Thursday, 16 July 2009 3:18 p.m. >>>>>>>>>> To: lib...@li... >>>>>>>>>> Subject: [libposix-development] bzip2 >>>>>>>>>> >>>>>>>>>> I've started implementing functions required by bzip2. I'm trying >>>>>>>>>> to >>>>>>>>>> implement them as simple as possible, with only the functionality >>>>>>>>>> required by bzip2. Example functions are fileno() and strerror(). >>>>>>>>>> I'll >>>>>>>>>> begin to implement open() in the next days. >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>> hd...@gm... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>>> ------ >>>>>>>>>> Enter the BlackBerry Developer Challenge >>>>>>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>>>>>> time, >>>>>>>>>> >>>>>>>>>> vendors submitting new applications to BlackBerry App World(TM) >>>>>>>>>> will >>>>>>>>>> have >>>>>>>>>> the opportunity to enter the BlackBerry Developer Challenge. See >>>>>>>>>> full >>>>>>>>>> prize >>>>>>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>>>>>> _______________________________________________ >>>>>>>>>> Libposix-development mailing list >>>>>>>>>> Lib...@li... >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> Enter the BlackBerry Developer Challenge >>>>>>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>>>>>> time, >>>>>>>>>> vendors submitting new applications to BlackBerry App World(TM) >>>>>>>>>> will >>>>>>>>>> have >>>>>>>>>> the opportunity to enter the BlackBerry Developer Challenge. See >>>>>>>>>> full >>>>>>>>>> prize >>>>>>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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... >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>>>>>> 30-Day >>>>>>> trial. Simplify your report design, integration and deployment - and >>>>>>> focus >>>>>>> on >>>>>>> what you do best, core application coding. Discover what's new with >>>>>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>>>>>> _______________________________________________ >>>>>>> Libposix-development mailing list >>>>>>> Lib...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> John Haitas >>>>>> jh...@gm... >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>>>>> 30-Day >>>>>> trial. Simplify your report design, integration and deployment - and >>>>>> focus >>>>>> on >>>>>> what you do best, core application coding. Discover what's new with >>>>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>>>>> _______________________________________________ >>>>>> Libposix-development mailing list >>>>>> Lib...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>>>> 30-Day >>>>> trial. Simplify your report design, integration and deployment - and >>>>> focus >>>>> on >>>>> what you do best, core application coding. Discover what's new with >>>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>> >>>> >>>> >>>> -- >>>> John Haitas >>>> jh...@gm... >>>> >>>> >>> >>> >>> >>> -- >>> John Haitas >>> jh...@gm... >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>> 30-Day >>> trial. Simplify your report design, integration and deployment - and >>> focus >>> on >>> what you do best, core application coding. Discover what's new with >>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > > > -- > John Haitas > jh...@gm... > > -- John Haitas jh...@gm... |
From: <jh...@gm...> - 2009-08-01 06:15:23
|
its not building on 64bit linux... [ 55%] Building C object CMakeFiles/posix.dir/mandatory/printf_scanner.c.o [ 58%] Building C object CMakeFiles/posix.dir/system/linux/system_calls.c.o /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c: In function ‘write’: /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:38: warning: cast to pointer from integer of different size /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c: In function ‘_Exit’: /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:44: warning: cast to pointer from integer of different size /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c: In function ‘mmap’: /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:62: error: ‘LINUX_SYS_mmap2’ undeclared (first use in this function) /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:62: error: (Each undeclared identifier is reported only once /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:62: error: for each function it appears in.) /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:63: warning: cast to pointer from integer of different size /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:63: warning: cast to pointer from integer of different size /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:64: warning: cast to pointer from integer of different size /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c: In function ‘system_open’: /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:75: warning: cast to pointer from integer of different size /home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5/system/linux/system_calls.c:76: warning: cast to pointer from integer of different size make[3]: *** [CMakeFiles/posix.dir/system/linux/system_calls.c.o] Error 1 make[3]: Leaving directory `/home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5' make[2]: *** [CMakeFiles/posix.dir/all] Error 2 make[2]: Leaving directory `/home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/jhaitas/src/build-area/libposix-0.0.3+git20090731t2300x80072a5' make: *** [build] Error 2 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 bzr: ERROR: The build failed. On Fri, Jul 31, 2009 at 9:00 PM, Henrique Almeida<hd...@gm...> wrote: > I've fixed the compilation for x86 and included mmap (I've changed > the sbrk call to mmap). I don't know yet if it compiles under other > platforms and I haven't tested on any platform, so expect crashes. > > 2009/7/31 <jh...@gm...>: >> The current HEAD doesn't build... My fault... >> >> >> On Fri, Jul 31, 2009 at 3:24 PM, <jh...@gm...> wrote: >>> >>> There is one error. Search for sbrk >>> >>> On Fri, Jul 31, 2009 at 2:10 PM, Henrique Almeida<hd...@gm...> wrote: >>>> >>>> Yes, that would be a good start. >>>> >>>> 2009/7/31 <jh...@gm...>: >>>>> >>>>> I could get us started by implementing the version of malloc taught in >>>>> K&R >>>>> C. >>>>> >>>>> Just an thought... >>>>> >>>>> On Fri, Jul 31, 2009 at 11:29 AM, Henrique Almeida<hd...@gm...> >>>>> wrote: >>>>>> >>>>>> I've spent too much time studying dlmalloc and there are still many >>>>>> details that I don't understand. I'm considering trying alternative >>>>>> implementations. >>>>>> >>>>>> 2009/7/22 Henrique Almeida <hd...@gm...>: >>>>>>> >>>>>>> I'm thinking about reimplementing Doug Lea's malloc for libposix, at >>>>>>> least while we don't have threading support. I'm currently studying >>>>>>> his implementation. malloc is an important function that we're >>>>>>> missing. >>>>>>> >>>>>>> 2009/7/16 Henrique Almeida <hd...@gm...>: >>>>>>>> >>>>>>>> 2009/7/16 Chris Forbes <ch...@fa...>: >>>>>>>>> >>>>>>>>> I think I've finally got git figured out (unwiring my brain from >>>>>>>>> using >>>>>>>>> SVN :(), >>>>>>>>> so I'll do some of the other functions for bzip2 after work. >>>>>>>> >>>>>>>> I have to write a git howto for the project, but I won't have time >>>>>>>> in >>>>>>>> the next weeks. The task is at TaskFreak site. Basically, git has two >>>>>>>> main differences from svn (that make things look complicated), which >>>>>>>> are multiple repositories (as a natural part of the development) and >>>>>>>> somewhat different terminology. So, to work with git you first need >>>>>>>> to >>>>>>>> recreate your own repository. Then you'll work by commiting >>>>>>>> frequently >>>>>>>> to your local repository. When the code is in a usable state for >>>>>>>> everyone, you merge your repository with SF repository. The commands >>>>>>>> are the following: >>>>>>>> >>>>>>>> # Create a full local clone of the remote repository (and setup >>>>>>>> remote >>>>>>>> merges) >>>>>>>> git clone ssh://hd...@li.../gitroot/libposix >>>>>>>> >>>>>>>> # Merge the remote repository in your local repository >>>>>>>> git pull >>>>>>>> >>>>>>>> # Merge the remote repository (other than SF) in your local >>>>>>>> repository >>>>>>>> git pull http://remote.repository.com/ >>>>>>>> >>>>>>>> # Edit code >>>>>>>> editor source1 source2 source3 (git is not used) >>>>>>>> >>>>>>>> # View list of changed files >>>>>>>> git status >>>>>>>> >>>>>>>> # View code changes >>>>>>>> git diff >>>>>>>> >>>>>>>> # Add files to commit >>>>>>>> git add source1/dir1 >>>>>>>> >>>>>>>> # Remove files >>>>>>>> git rm source1 >>>>>>>> >>>>>>>> # Move files >>>>>>>> git mv source1 dest1 >>>>>>>> >>>>>>>> # View code changes that were marked as added to commit (with git >>>>>>>> add) >>>>>>>> git diff HEAD >>>>>>>> >>>>>>>> # Commit (to the local repository) >>>>>>>> git commit >>>>>>>> >>>>>>>> # View the commit log >>>>>>>> git log >>>>>>>> >>>>>>>> # Merge the local repository to the remote repository (upload code >>>>>>>> to >>>>>>>> SF) >>>>>>>> git push >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> -- Chris >>>>>>>>> >>>>>>>>> -----Original Message----- >>>>>>>>> From: Henrique Almeida [mailto:hd...@gm...] >>>>>>>>> Sent: Thursday, 16 July 2009 3:18 p.m. >>>>>>>>> To: lib...@li... >>>>>>>>> Subject: [libposix-development] bzip2 >>>>>>>>> >>>>>>>>> I've started implementing functions required by bzip2. I'm trying >>>>>>>>> to >>>>>>>>> implement them as simple as possible, with only the functionality >>>>>>>>> required by bzip2. Example functions are fileno() and strerror(). >>>>>>>>> I'll >>>>>>>>> begin to implement open() in the next days. >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Henrique Dante de Almeida >>>>>>>>> hd...@gm... >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>> ------ >>>>>>>>> Enter the BlackBerry Developer Challenge >>>>>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>>>>> time, >>>>>>>>> >>>>>>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>>>>>> have >>>>>>>>> the opportunity to enter the BlackBerry Developer Challenge. See >>>>>>>>> full >>>>>>>>> prize >>>>>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>>>>> _______________________________________________ >>>>>>>>> Libposix-development mailing list >>>>>>>>> Lib...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> Enter the BlackBerry Developer Challenge >>>>>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>>>>> time, >>>>>>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>>>>>> have >>>>>>>>> the opportunity to enter the BlackBerry Developer Challenge. See >>>>>>>>> full >>>>>>>>> prize >>>>>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>>>>> _______________________________________________ >>>>>>>>> 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... >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>>>>> 30-Day >>>>>> trial. Simplify your report design, integration and deployment - and >>>>>> focus >>>>>> on >>>>>> what you do best, core application coding. Discover what's new with >>>>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>>>>> _______________________________________________ >>>>>> Libposix-development mailing list >>>>>> Lib...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> John Haitas >>>>> jh...@gm... >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>>>> 30-Day >>>>> trial. Simplify your report design, integration and deployment - and >>>>> focus >>>>> on >>>>> what you do best, core application coding. Discover what's new with >>>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>>> 30-Day >>>> trial. Simplify your report design, integration and deployment - and >>>> focus >>>> on >>>> what you do best, core application coding. Discover what's new with >>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>> >>> >>> >>> -- >>> John Haitas >>> jh...@gm... >>> >>> >> >> >> >> -- >> John Haitas >> jh...@gm... >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- John Haitas jh...@gm... |
From: Henrique A. <hd...@gm...> - 2009-08-01 02:00:51
|
I've fixed the compilation for x86 and included mmap (I've changed the sbrk call to mmap). I don't know yet if it compiles under other platforms and I haven't tested on any platform, so expect crashes. 2009/7/31 <jh...@gm...>: > The current HEAD doesn't build... My fault... > > > On Fri, Jul 31, 2009 at 3:24 PM, <jh...@gm...> wrote: >> >> There is one error. Search for sbrk >> >> On Fri, Jul 31, 2009 at 2:10 PM, Henrique Almeida<hd...@gm...> wrote: >>> >>> Yes, that would be a good start. >>> >>> 2009/7/31 <jh...@gm...>: >>>> >>>> I could get us started by implementing the version of malloc taught in >>>> K&R >>>> C. >>>> >>>> Just an thought... >>>> >>>> On Fri, Jul 31, 2009 at 11:29 AM, Henrique Almeida<hd...@gm...> >>>> wrote: >>>>> >>>>> I've spent too much time studying dlmalloc and there are still many >>>>> details that I don't understand. I'm considering trying alternative >>>>> implementations. >>>>> >>>>> 2009/7/22 Henrique Almeida <hd...@gm...>: >>>>>> >>>>>> I'm thinking about reimplementing Doug Lea's malloc for libposix, at >>>>>> least while we don't have threading support. I'm currently studying >>>>>> his implementation. malloc is an important function that we're >>>>>> missing. >>>>>> >>>>>> 2009/7/16 Henrique Almeida <hd...@gm...>: >>>>>>> >>>>>>> 2009/7/16 Chris Forbes <ch...@fa...>: >>>>>>>> >>>>>>>> I think I've finally got git figured out (unwiring my brain from >>>>>>>> using >>>>>>>> SVN :(), >>>>>>>> so I'll do some of the other functions for bzip2 after work. >>>>>>> >>>>>>> I have to write a git howto for the project, but I won't have time >>>>>>> in >>>>>>> the next weeks. The task is at TaskFreak site. Basically, git has two >>>>>>> main differences from svn (that make things look complicated), which >>>>>>> are multiple repositories (as a natural part of the development) and >>>>>>> somewhat different terminology. So, to work with git you first need >>>>>>> to >>>>>>> recreate your own repository. Then you'll work by commiting >>>>>>> frequently >>>>>>> to your local repository. When the code is in a usable state for >>>>>>> everyone, you merge your repository with SF repository. The commands >>>>>>> are the following: >>>>>>> >>>>>>> # Create a full local clone of the remote repository (and setup >>>>>>> remote >>>>>>> merges) >>>>>>> git clone ssh://hd...@li.../gitroot/libposix >>>>>>> >>>>>>> # Merge the remote repository in your local repository >>>>>>> git pull >>>>>>> >>>>>>> # Merge the remote repository (other than SF) in your local >>>>>>> repository >>>>>>> git pull http://remote.repository.com/ >>>>>>> >>>>>>> # Edit code >>>>>>> editor source1 source2 source3 (git is not used) >>>>>>> >>>>>>> # View list of changed files >>>>>>> git status >>>>>>> >>>>>>> # View code changes >>>>>>> git diff >>>>>>> >>>>>>> # Add files to commit >>>>>>> git add source1/dir1 >>>>>>> >>>>>>> # Remove files >>>>>>> git rm source1 >>>>>>> >>>>>>> # Move files >>>>>>> git mv source1 dest1 >>>>>>> >>>>>>> # View code changes that were marked as added to commit (with git >>>>>>> add) >>>>>>> git diff HEAD >>>>>>> >>>>>>> # Commit (to the local repository) >>>>>>> git commit >>>>>>> >>>>>>> # View the commit log >>>>>>> git log >>>>>>> >>>>>>> # Merge the local repository to the remote repository (upload code >>>>>>> to >>>>>>> SF) >>>>>>> git push >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> -- Chris >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Henrique Almeida [mailto:hd...@gm...] >>>>>>>> Sent: Thursday, 16 July 2009 3:18 p.m. >>>>>>>> To: lib...@li... >>>>>>>> Subject: [libposix-development] bzip2 >>>>>>>> >>>>>>>> I've started implementing functions required by bzip2. I'm trying >>>>>>>> to >>>>>>>> implement them as simple as possible, with only the functionality >>>>>>>> required by bzip2. Example functions are fileno() and strerror(). >>>>>>>> I'll >>>>>>>> begin to implement open() in the next days. >>>>>>>> >>>>>>>> -- >>>>>>>> Henrique Dante de Almeida >>>>>>>> hd...@gm... >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------ >>>>>>>> ------ >>>>>>>> Enter the BlackBerry Developer Challenge >>>>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>>>> time, >>>>>>>> >>>>>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>>>>> have >>>>>>>> the opportunity to enter the BlackBerry Developer Challenge. See >>>>>>>> full >>>>>>>> prize >>>>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>>>> _______________________________________________ >>>>>>>> Libposix-development mailing list >>>>>>>> Lib...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> Enter the BlackBerry Developer Challenge >>>>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>>>> time, >>>>>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>>>>> have >>>>>>>> the opportunity to enter the BlackBerry Developer Challenge. See >>>>>>>> full >>>>>>>> prize >>>>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>>>> _______________________________________________ >>>>>>>> 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... >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>>>> 30-Day >>>>> trial. Simplify your report design, integration and deployment - and >>>>> focus >>>>> on >>>>> what you do best, core application coding. Discover what's new with >>>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>> >>>> >>>> >>>> -- >>>> John Haitas >>>> jh...@gm... >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>>> 30-Day >>>> trial. Simplify your report design, integration and deployment - and >>>> focus >>>> on >>>> what you do best, core application coding. Discover what's new with >>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>> 30-Day >>> trial. Simplify your report design, integration and deployment - and >>> focus >>> on >>> what you do best, core application coding. Discover what's new with >>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >> >> >> >> -- >> John Haitas >> jh...@gm... >> >> > > > > -- > John Haitas > jh...@gm... > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
From: <jh...@gm...> - 2009-07-31 20:35:20
|
The current HEAD doesn't build... My fault... On Fri, Jul 31, 2009 at 3:24 PM, <jh...@gm...> wrote: > There is one error. Search for sbrk > > On Fri, Jul 31, 2009 at 2:10 PM, Henrique Almeida<hd...@gm...> wrote: >> >> Yes, that would be a good start. >> >> 2009/7/31 <jh...@gm...>: >>> >>> I could get us started by implementing the version of malloc taught in >>> K&R >>> C. >>> >>> Just an thought... >>> >>> On Fri, Jul 31, 2009 at 11:29 AM, Henrique Almeida<hd...@gm...> >>> wrote: >>>> >>>> I've spent too much time studying dlmalloc and there are still many >>>> details that I don't understand. I'm considering trying alternative >>>> implementations. >>>> >>>> 2009/7/22 Henrique Almeida <hd...@gm...>: >>>>> >>>>> I'm thinking about reimplementing Doug Lea's malloc for libposix, at >>>>> least while we don't have threading support. I'm currently studying >>>>> his implementation. malloc is an important function that we're >>>>> missing. >>>>> >>>>> 2009/7/16 Henrique Almeida <hd...@gm...>: >>>>>> >>>>>> 2009/7/16 Chris Forbes <ch...@fa...>: >>>>>>> >>>>>>> I think I've finally got git figured out (unwiring my brain from >>>>>>> using >>>>>>> SVN :(), >>>>>>> so I'll do some of the other functions for bzip2 after work. >>>>>> >>>>>> I have to write a git howto for the project, but I won't have time in >>>>>> the next weeks. The task is at TaskFreak site. Basically, git has two >>>>>> main differences from svn (that make things look complicated), which >>>>>> are multiple repositories (as a natural part of the development) and >>>>>> somewhat different terminology. So, to work with git you first need to >>>>>> recreate your own repository. Then you'll work by commiting frequently >>>>>> to your local repository. When the code is in a usable state for >>>>>> everyone, you merge your repository with SF repository. The commands >>>>>> are the following: >>>>>> >>>>>> # Create a full local clone of the remote repository (and setup >>>>>> remote >>>>>> merges) >>>>>> git clone ssh://hd...@li.../gitroot/libposix >>>>>> >>>>>> # Merge the remote repository in your local repository >>>>>> git pull >>>>>> >>>>>> # Merge the remote repository (other than SF) in your local >>>>>> repository >>>>>> git pull http://remote.repository.com/ >>>>>> >>>>>> # Edit code >>>>>> editor source1 source2 source3 (git is not used) >>>>>> >>>>>> # View list of changed files >>>>>> git status >>>>>> >>>>>> # View code changes >>>>>> git diff >>>>>> >>>>>> # Add files to commit >>>>>> git add source1/dir1 >>>>>> >>>>>> # Remove files >>>>>> git rm source1 >>>>>> >>>>>> # Move files >>>>>> git mv source1 dest1 >>>>>> >>>>>> # View code changes that were marked as added to commit (with git >>>>>> add) >>>>>> git diff HEAD >>>>>> >>>>>> # Commit (to the local repository) >>>>>> git commit >>>>>> >>>>>> # View the commit log >>>>>> git log >>>>>> >>>>>> # Merge the local repository to the remote repository (upload code to >>>>>> SF) >>>>>> git push >>>>>> >>>>>> >>>>>>> >>>>>>> -- Chris >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Henrique Almeida [mailto:hd...@gm...] >>>>>>> Sent: Thursday, 16 July 2009 3:18 p.m. >>>>>>> To: lib...@li... >>>>>>> Subject: [libposix-development] bzip2 >>>>>>> >>>>>>> I've started implementing functions required by bzip2. I'm trying to >>>>>>> implement them as simple as possible, with only the functionality >>>>>>> required by bzip2. Example functions are fileno() and strerror(). >>>>>>> I'll >>>>>>> begin to implement open() in the next days. >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------ >>>>>>> ------ >>>>>>> Enter the BlackBerry Developer Challenge >>>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>>> time, >>>>>>> >>>>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>>>> have >>>>>>> the opportunity to enter the BlackBerry Developer Challenge. See full >>>>>>> prize >>>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>>> _______________________________________________ >>>>>>> Libposix-development mailing list >>>>>>> Lib...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Enter the BlackBerry Developer Challenge >>>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>>> time, >>>>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>>>> have >>>>>>> the opportunity to enter the BlackBerry Developer Challenge. See full >>>>>>> prize >>>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>>> _______________________________________________ >>>>>>> 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... >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>>> 30-Day >>>> trial. Simplify your report design, integration and deployment - and >>>> focus >>>> on >>>> what you do best, core application coding. Discover what's new with >>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>> >>> >>> >>> -- >>> John Haitas >>> jh...@gm... >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>> 30-Day >>> trial. Simplify your report design, integration and deployment - and >>> focus >>> on >>> what you do best, core application coding. Discover what's new with >>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > > > -- > John Haitas > jh...@gm... > > -- John Haitas jh...@gm... |
From: <jh...@gm...> - 2009-07-31 20:24:59
|
There is one error. Search for sbrk On Fri, Jul 31, 2009 at 2:10 PM, Henrique Almeida<hd...@gm...> wrote: > Yes, that would be a good start. > > 2009/7/31 <jh...@gm...>: >> I could get us started by implementing the version of malloc taught in K&R >> C. >> >> Just an thought... >> >> On Fri, Jul 31, 2009 at 11:29 AM, Henrique Almeida<hd...@gm...> wrote: >>> >>> I've spent too much time studying dlmalloc and there are still many >>> details that I don't understand. I'm considering trying alternative >>> implementations. >>> >>> 2009/7/22 Henrique Almeida <hd...@gm...>: >>>> >>>> I'm thinking about reimplementing Doug Lea's malloc for libposix, at >>>> least while we don't have threading support. I'm currently studying >>>> his implementation. malloc is an important function that we're >>>> missing. >>>> >>>> 2009/7/16 Henrique Almeida <hd...@gm...>: >>>>> >>>>> 2009/7/16 Chris Forbes <ch...@fa...>: >>>>>> >>>>>> I think I've finally got git figured out (unwiring my brain from using >>>>>> SVN :(), >>>>>> so I'll do some of the other functions for bzip2 after work. >>>>> >>>>> I have to write a git howto for the project, but I won't have time in >>>>> the next weeks. The task is at TaskFreak site. Basically, git has two >>>>> main differences from svn (that make things look complicated), which >>>>> are multiple repositories (as a natural part of the development) and >>>>> somewhat different terminology. So, to work with git you first need to >>>>> recreate your own repository. Then you'll work by commiting frequently >>>>> to your local repository. When the code is in a usable state for >>>>> everyone, you merge your repository with SF repository. The commands >>>>> are the following: >>>>> >>>>> # Create a full local clone of the remote repository (and setup remote >>>>> merges) >>>>> git clone ssh://hd...@li.../gitroot/libposix >>>>> >>>>> # Merge the remote repository in your local repository >>>>> git pull >>>>> >>>>> # Merge the remote repository (other than SF) in your local repository >>>>> git pull http://remote.repository.com/ >>>>> >>>>> # Edit code >>>>> editor source1 source2 source3 (git is not used) >>>>> >>>>> # View list of changed files >>>>> git status >>>>> >>>>> # View code changes >>>>> git diff >>>>> >>>>> # Add files to commit >>>>> git add source1/dir1 >>>>> >>>>> # Remove files >>>>> git rm source1 >>>>> >>>>> # Move files >>>>> git mv source1 dest1 >>>>> >>>>> # View code changes that were marked as added to commit (with git add) >>>>> git diff HEAD >>>>> >>>>> # Commit (to the local repository) >>>>> git commit >>>>> >>>>> # View the commit log >>>>> git log >>>>> >>>>> # Merge the local repository to the remote repository (upload code to >>>>> SF) >>>>> git push >>>>> >>>>> >>>>>> >>>>>> -- Chris >>>>>> >>>>>> -----Original Message----- >>>>>> From: Henrique Almeida [mailto:hd...@gm...] >>>>>> Sent: Thursday, 16 July 2009 3:18 p.m. >>>>>> To: lib...@li... >>>>>> Subject: [libposix-development] bzip2 >>>>>> >>>>>> I've started implementing functions required by bzip2. I'm trying to >>>>>> implement them as simple as possible, with only the functionality >>>>>> required by bzip2. Example functions are fileno() and strerror(). I'll >>>>>> begin to implement open() in the next days. >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> ------ >>>>>> Enter the BlackBerry Developer Challenge >>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>> time, >>>>>> >>>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>>> have >>>>>> the opportunity to enter the BlackBerry Developer Challenge. See full >>>>>> prize >>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>> _______________________________________________ >>>>>> Libposix-development mailing list >>>>>> Lib...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Enter the BlackBerry Developer Challenge >>>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>>> time, >>>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>>> have >>>>>> the opportunity to enter the BlackBerry Developer Challenge. See full >>>>>> prize >>>>>> details at: http://p.sf.net/sfu/Challenge >>>>>> _______________________________________________ >>>>>> 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... >>> >>> >>> ------------------------------------------------------------------------------ >>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >>> 30-Day >>> trial. Simplify your report design, integration and deployment - and focus >>> on >>> what you do best, core application coding. Discover what's new with >>> Crystal Reports now. http://p.sf.net/sfu/bobj-july >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >> >> >> >> -- >> John Haitas >> jh...@gm... >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- John Haitas jh...@gm... |
From: Henrique A. <hd...@gm...> - 2009-07-31 19:11:12
|
Yes, that would be a good start. 2009/7/31 <jh...@gm...>: > I could get us started by implementing the version of malloc taught in K&R > C. > > Just an thought... > > On Fri, Jul 31, 2009 at 11:29 AM, Henrique Almeida<hd...@gm...> wrote: >> >> I've spent too much time studying dlmalloc and there are still many >> details that I don't understand. I'm considering trying alternative >> implementations. >> >> 2009/7/22 Henrique Almeida <hd...@gm...>: >>> >>> I'm thinking about reimplementing Doug Lea's malloc for libposix, at >>> least while we don't have threading support. I'm currently studying >>> his implementation. malloc is an important function that we're >>> missing. >>> >>> 2009/7/16 Henrique Almeida <hd...@gm...>: >>>> >>>> 2009/7/16 Chris Forbes <ch...@fa...>: >>>>> >>>>> I think I've finally got git figured out (unwiring my brain from using >>>>> SVN :(), >>>>> so I'll do some of the other functions for bzip2 after work. >>>> >>>> I have to write a git howto for the project, but I won't have time in >>>> the next weeks. The task is at TaskFreak site. Basically, git has two >>>> main differences from svn (that make things look complicated), which >>>> are multiple repositories (as a natural part of the development) and >>>> somewhat different terminology. So, to work with git you first need to >>>> recreate your own repository. Then you'll work by commiting frequently >>>> to your local repository. When the code is in a usable state for >>>> everyone, you merge your repository with SF repository. The commands >>>> are the following: >>>> >>>> # Create a full local clone of the remote repository (and setup remote >>>> merges) >>>> git clone ssh://hd...@li.../gitroot/libposix >>>> >>>> # Merge the remote repository in your local repository >>>> git pull >>>> >>>> # Merge the remote repository (other than SF) in your local repository >>>> git pull http://remote.repository.com/ >>>> >>>> # Edit code >>>> editor source1 source2 source3 (git is not used) >>>> >>>> # View list of changed files >>>> git status >>>> >>>> # View code changes >>>> git diff >>>> >>>> # Add files to commit >>>> git add source1/dir1 >>>> >>>> # Remove files >>>> git rm source1 >>>> >>>> # Move files >>>> git mv source1 dest1 >>>> >>>> # View code changes that were marked as added to commit (with git add) >>>> git diff HEAD >>>> >>>> # Commit (to the local repository) >>>> git commit >>>> >>>> # View the commit log >>>> git log >>>> >>>> # Merge the local repository to the remote repository (upload code to >>>> SF) >>>> git push >>>> >>>> >>>>> >>>>> -- Chris >>>>> >>>>> -----Original Message----- >>>>> From: Henrique Almeida [mailto:hd...@gm...] >>>>> Sent: Thursday, 16 July 2009 3:18 p.m. >>>>> To: lib...@li... >>>>> Subject: [libposix-development] bzip2 >>>>> >>>>> I've started implementing functions required by bzip2. I'm trying to >>>>> implement them as simple as possible, with only the functionality >>>>> required by bzip2. Example functions are fileno() and strerror(). I'll >>>>> begin to implement open() in the next days. >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>>> >>>>> ------------------------------------------------------------------------ >>>>> ------ >>>>> Enter the BlackBerry Developer Challenge >>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>> time, >>>>> >>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>> have >>>>> the opportunity to enter the BlackBerry Developer Challenge. See full >>>>> prize >>>>> details at: http://p.sf.net/sfu/Challenge >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Enter the BlackBerry Developer Challenge >>>>> This is your chance to win up to $100,000 in prizes! For a limited >>>>> time, >>>>> vendors submitting new applications to BlackBerry App World(TM) will >>>>> have >>>>> the opportunity to enter the BlackBerry Developer Challenge. See full >>>>> prize >>>>> details at: http://p.sf.net/sfu/Challenge >>>>> _______________________________________________ >>>>> 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... >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > > > -- > John Haitas > jh...@gm... > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > -- Henrique Dante de Almeida hd...@gm... |
From: <jh...@gm...> - 2009-07-31 17:57:21
|
I could get us started by implementing the version of malloc taught in K&R C. Just an thought... On Fri, Jul 31, 2009 at 11:29 AM, Henrique Almeida<hd...@gm...> wrote: > I've spent too much time studying dlmalloc and there are still many > details that I don't understand. I'm considering trying alternative > implementations. > > 2009/7/22 Henrique Almeida <hd...@gm...>: >> I'm thinking about reimplementing Doug Lea's malloc for libposix, at >> least while we don't have threading support. I'm currently studying >> his implementation. malloc is an important function that we're >> missing. >> >> 2009/7/16 Henrique Almeida <hd...@gm...>: >>> 2009/7/16 Chris Forbes <ch...@fa...>: >>>> I think I've finally got git figured out (unwiring my brain from using >>>> SVN :(), >>>> so I'll do some of the other functions for bzip2 after work. >>> >>> I have to write a git howto for the project, but I won't have time in >>> the next weeks. The task is at TaskFreak site. Basically, git has two >>> main differences from svn (that make things look complicated), which >>> are multiple repositories (as a natural part of the development) and >>> somewhat different terminology. So, to work with git you first need to >>> recreate your own repository. Then you'll work by commiting frequently >>> to your local repository. When the code is in a usable state for >>> everyone, you merge your repository with SF repository. The commands >>> are the following: >>> >>> # Create a full local clone of the remote repository (and setup remote merges) >>> git clone ssh://hd...@li.../gitroot/libposix >>> >>> # Merge the remote repository in your local repository >>> git pull >>> >>> # Merge the remote repository (other than SF) in your local repository >>> git pull http://remote.repository.com/ >>> >>> # Edit code >>> editor source1 source2 source3 (git is not used) >>> >>> # View list of changed files >>> git status >>> >>> # View code changes >>> git diff >>> >>> # Add files to commit >>> git add source1/dir1 >>> >>> # Remove files >>> git rm source1 >>> >>> # Move files >>> git mv source1 dest1 >>> >>> # View code changes that were marked as added to commit (with git add) >>> git diff HEAD >>> >>> # Commit (to the local repository) >>> git commit >>> >>> # View the commit log >>> git log >>> >>> # Merge the local repository to the remote repository (upload code to SF) >>> git push >>> >>> >>>> >>>> -- Chris >>>> >>>> -----Original Message----- >>>> From: Henrique Almeida [mailto:hd...@gm...] >>>> Sent: Thursday, 16 July 2009 3:18 p.m. >>>> To: lib...@li... >>>> Subject: [libposix-development] bzip2 >>>> >>>> I've started implementing functions required by bzip2. I'm trying to >>>> implement them as simple as possible, with only the functionality >>>> required by bzip2. Example functions are fileno() and strerror(). I'll >>>> begin to implement open() in the next days. >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>>> ------------------------------------------------------------------------ >>>> ------ >>>> Enter the BlackBerry Developer Challenge >>>> This is your chance to win up to $100,000 in prizes! For a limited time, >>>> >>>> vendors submitting new applications to BlackBerry App World(TM) will >>>> have >>>> the opportunity to enter the BlackBerry Developer Challenge. See full >>>> prize >>>> details at: http://p.sf.net/sfu/Challenge >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>>> ------------------------------------------------------------------------------ >>>> Enter the BlackBerry Developer Challenge >>>> This is your chance to win up to $100,000 in prizes! For a limited time, >>>> vendors submitting new applications to BlackBerry App World(TM) will have >>>> the opportunity to enter the BlackBerry Developer Challenge. See full prize >>>> details at: http://p.sf.net/sfu/Challenge >>>> _______________________________________________ >>>> 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... > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- John Haitas jh...@gm... |
From: Henrique A. <hd...@gm...> - 2009-07-31 16:29:54
|
I've spent too much time studying dlmalloc and there are still many details that I don't understand. I'm considering trying alternative implementations. 2009/7/22 Henrique Almeida <hd...@gm...>: > I'm thinking about reimplementing Doug Lea's malloc for libposix, at > least while we don't have threading support. I'm currently studying > his implementation. malloc is an important function that we're > missing. > > 2009/7/16 Henrique Almeida <hd...@gm...>: >> 2009/7/16 Chris Forbes <ch...@fa...>: >>> I think I've finally got git figured out (unwiring my brain from using >>> SVN :(), >>> so I'll do some of the other functions for bzip2 after work. >> >> I have to write a git howto for the project, but I won't have time in >> the next weeks. The task is at TaskFreak site. Basically, git has two >> main differences from svn (that make things look complicated), which >> are multiple repositories (as a natural part of the development) and >> somewhat different terminology. So, to work with git you first need to >> recreate your own repository. Then you'll work by commiting frequently >> to your local repository. When the code is in a usable state for >> everyone, you merge your repository with SF repository. The commands >> are the following: >> >> # Create a full local clone of the remote repository (and setup remote merges) >> git clone ssh://hd...@li.../gitroot/libposix >> >> # Merge the remote repository in your local repository >> git pull >> >> # Merge the remote repository (other than SF) in your local repository >> git pull http://remote.repository.com/ >> >> # Edit code >> editor source1 source2 source3 (git is not used) >> >> # View list of changed files >> git status >> >> # View code changes >> git diff >> >> # Add files to commit >> git add source1/dir1 >> >> # Remove files >> git rm source1 >> >> # Move files >> git mv source1 dest1 >> >> # View code changes that were marked as added to commit (with git add) >> git diff HEAD >> >> # Commit (to the local repository) >> git commit >> >> # View the commit log >> git log >> >> # Merge the local repository to the remote repository (upload code to SF) >> git push >> >> >>> >>> -- Chris >>> >>> -----Original Message----- >>> From: Henrique Almeida [mailto:hd...@gm...] >>> Sent: Thursday, 16 July 2009 3:18 p.m. >>> To: lib...@li... >>> Subject: [libposix-development] bzip2 >>> >>> I've started implementing functions required by bzip2. I'm trying to >>> implement them as simple as possible, with only the functionality >>> required by bzip2. Example functions are fileno() and strerror(). I'll >>> begin to implement open() in the next days. >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >>> ------------------------------------------------------------------------ >>> ------ >>> Enter the BlackBerry Developer Challenge >>> This is your chance to win up to $100,000 in prizes! For a limited time, >>> >>> vendors submitting new applications to BlackBerry App World(TM) will >>> have >>> the opportunity to enter the BlackBerry Developer Challenge. See full >>> prize >>> details at: http://p.sf.net/sfu/Challenge >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >>> ------------------------------------------------------------------------------ >>> Enter the BlackBerry Developer Challenge >>> This is your chance to win up to $100,000 in prizes! For a limited time, >>> vendors submitting new applications to BlackBerry App World(TM) will have >>> the opportunity to enter the BlackBerry Developer Challenge. See full prize >>> details at: http://p.sf.net/sfu/Challenge >>> _______________________________________________ >>> 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... |
From: Henrique A. <hd...@gm...> - 2009-07-23 00:09:34
|
I'm thinking about reimplementing Doug Lea's malloc for libposix, at least while we don't have threading support. I'm currently studying his implementation. malloc is an important function that we're missing. 2009/7/16 Henrique Almeida <hd...@gm...>: > 2009/7/16 Chris Forbes <ch...@fa...>: >> I think I've finally got git figured out (unwiring my brain from using >> SVN :(), >> so I'll do some of the other functions for bzip2 after work. > > I have to write a git howto for the project, but I won't have time in > the next weeks. The task is at TaskFreak site. Basically, git has two > main differences from svn (that make things look complicated), which > are multiple repositories (as a natural part of the development) and > somewhat different terminology. So, to work with git you first need to > recreate your own repository. Then you'll work by commiting frequently > to your local repository. When the code is in a usable state for > everyone, you merge your repository with SF repository. The commands > are the following: > > # Create a full local clone of the remote repository (and setup remote merges) > git clone ssh://hd...@li.../gitroot/libposix > > # Merge the remote repository in your local repository > git pull > > # Merge the remote repository (other than SF) in your local repository > git pull http://remote.repository.com/ > > # Edit code > editor source1 source2 source3 (git is not used) > > # View list of changed files > git status > > # View code changes > git diff > > # Add files to commit > git add source1/dir1 > > # Remove files > git rm source1 > > # Move files > git mv source1 dest1 > > # View code changes that were marked as added to commit (with git add) > git diff HEAD > > # Commit (to the local repository) > git commit > > # View the commit log > git log > > # Merge the local repository to the remote repository (upload code to SF) > git push > > >> >> -- Chris >> >> -----Original Message----- >> From: Henrique Almeida [mailto:hd...@gm...] >> Sent: Thursday, 16 July 2009 3:18 p.m. >> To: lib...@li... >> Subject: [libposix-development] bzip2 >> >> I've started implementing functions required by bzip2. I'm trying to >> implement them as simple as possible, with only the functionality >> required by bzip2. Example functions are fileno() and strerror(). I'll >> begin to implement open() in the next days. >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> ------------------------------------------------------------------------ >> ------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> >> vendors submitting new applications to BlackBerry App World(TM) will >> have >> the opportunity to enter the BlackBerry Developer Challenge. See full >> prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> 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-07-16 17:22:59
|
Someone has also suggested flyspray. I'll also take a look on that. 2009/7/15 Henrique Almeida <hd...@gm...>: > I'll take a look. > > 2009/7/15 John Haitas <jh...@gm...>: >> Trac is good >> >> On Wed, Jul 15, 2009 at 4:03 PM, Chris Forbes<ch...@fa...> wrote: >>> I've used Trac quite successfully. >>> >>> -----Original Message----- >>> From: Henrique Almeida [mailto:hd...@gm...] >>> Sent: Wednesday, 15 July 2009 2:41 p.m. >>> To: lib...@li... >>> Subject: [libposix-development] TaskFreak broken >>> >>> TaskFreak has been broken for almost one week and I'm unable to edit >>> or create tasks. SF folks are not very fast to solve such issues. So, >>> I'm thinking about finding another task manager for the project. I'd >>> appreciate if anyone can suggest whatever todo, bugzilla, workflow, >>> etc. application that could fill the hole. Bonus for applications that >>> have the following features: >>> >>> - task categorization (for Testing, C Development, etc.) >>> - task dependencies (depends on, suggests, recommends, etc.) >>> - priority indicator (urgent, low, etc.) >>> - adding comments to tasks >>> - graphical preview of task status (0%, 20% 40%, etc.) >>> - full anonymous read-only access (to tasks, category filters, >>> comments, etc.) >>> - clean, user friendly interface >>> >>> I'll give you 1 billion dollars if you bring me a task manager with >>> all the features above (not really). >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >>> ------------------------------------------------------------------------ >>> ------ >>> Enter the BlackBerry Developer Challenge >>> This is your chance to win up to $100,000 in prizes! For a limited time, >>> >>> vendors submitting new applications to BlackBerry App World(TM) will >>> have >>> the opportunity to enter the BlackBerry Developer Challenge. See full >>> prize >>> details at: http://p.sf.net/sfu/Challenge >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >>> ------------------------------------------------------------------------------ >>> Enter the BlackBerry Developer Challenge >>> This is your chance to win up to $100,000 in prizes! For a limited time, >>> vendors submitting new applications to BlackBerry App World(TM) will have >>> the opportunity to enter the BlackBerry Developer Challenge. See full prize >>> details at: http://p.sf.net/sfu/Challenge >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >> >> >> >> -- >> John Haitas >> jh...@gm... >> >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> 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-07-16 17:22:15
|
2009/7/16 Chris Forbes <ch...@fa...>: > I think I've finally got git figured out (unwiring my brain from using > SVN :(), > so I'll do some of the other functions for bzip2 after work. I have to write a git howto for the project, but I won't have time in the next weeks. The task is at TaskFreak site. Basically, git has two main differences from svn (that make things look complicated), which are multiple repositories (as a natural part of the development) and somewhat different terminology. So, to work with git you first need to recreate your own repository. Then you'll work by commiting frequently to your local repository. When the code is in a usable state for everyone, you merge your repository with SF repository. The commands are the following: # Create a full local clone of the remote repository (and setup remote merges) git clone ssh://hd...@li.../gitroot/libposix # Merge the remote repository in your local repository git pull # Merge the remote repository (other than SF) in your local repository git pull http://remote.repository.com/ # Edit code editor source1 source2 source3 (git is not used) # View list of changed files git status # View code changes git diff # Add files to commit git add source1/dir1 # Remove files git rm source1 # Move files git mv source1 dest1 # View code changes that were marked as added to commit (with git add) git diff HEAD # Commit (to the local repository) git commit # View the commit log git log # Merge the local repository to the remote repository (upload code to SF) git push > > -- Chris > > -----Original Message----- > From: Henrique Almeida [mailto:hd...@gm...] > Sent: Thursday, 16 July 2009 3:18 p.m. > To: lib...@li... > Subject: [libposix-development] bzip2 > > I've started implementing functions required by bzip2. I'm trying to > implement them as simple as possible, with only the functionality > required by bzip2. Example functions are fileno() and strerror(). I'll > begin to implement open() in the next days. > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------ > ------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > > vendors submitting new applications to BlackBerry App World(TM) will > have > the opportunity to enter the BlackBerry Developer Challenge. See full > prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > 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-07-16 17:07:01
|
2009/7/16 Chris Forbes <ch...@fa...>: > My point was to avoid having to do `add_posix_test()` in a cmake config file someplace; Instead I automatically determine the tests that exist, In that case I don't think that's necessary. Isolating the build system from code has more advantages than disadvantages. For example, it's easier to replace the build system and people that need to copy the test code to their own projects don't need to worry about the extra markup code. I'm planning splitting the main make file and moving test rules to the tests directory (this task is available at TaskFreak), so that the test list can grow without messing the root CMakeLists.txt. The goal is to have a very simple 1 or 2 line command sequence for specifying tests, for example: add_libposix_test(test_name source1 source2 source3 [INPUT input_file] [EXPECTED_OUPUT output_file] [EXPECTED_ERROR error_file] [INVERT_RESULT]) > and specify their dependencies at the same point where the test is defined (in the C file). > -- Henrique Dante de Almeida hd...@gm... |
From: Chris F. <ch...@fa...> - 2009-07-16 03:21:44
|
I think I've finally got git figured out (unwiring my brain from using SVN :(), so I'll do some of the other functions for bzip2 after work. -- Chris -----Original Message----- From: Henrique Almeida [mailto:hd...@gm...] Sent: Thursday, 16 July 2009 3:18 p.m. To: lib...@li... Subject: [libposix-development] bzip2 I've started implementing functions required by bzip2. I'm trying to implement them as simple as possible, with only the functionality required by bzip2. Example functions are fileno() and strerror(). I'll begin to implement open() in the next days. -- Henrique Dante de Almeida hd...@gm... ------------------------------------------------------------------------ ------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Libposix-development mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libposix-development |
From: Chris F. <ch...@fa...> - 2009-07-16 03:18:43
|
My point was to avoid having to do `add_posix_test()` in a cmake config file someplace; Instead I automatically determine the tests that exist, and specify their dependencies at the same point where the test is defined (in the C file). -----Original Message----- From: Henrique Almeida [mailto:hd...@gm...] Sent: Thursday, 16 July 2009 3:10 p.m. To: lib...@li... Subject: Re: [libposix-development] [PATCH] strncpy implementation and tests If I understood correctly, CTest is already providing that functionallity. For TEST(), we have add_libposix_test(), which works the same way. The test script is automatically provided by CTest. For example, if I run "make test" on my system I get: Running tests... Start processing tests Test project /home/hdante/código/libposix/libposix.build 1/ 6 Testing puts_hello Passed 2/ 6 Testing hello Passed 3/ 6 Testing printf_scanner Passed 4/ 6 Testing print_parser Passed 5/ 6 Testing strncpy Passed 6/ 6 Testing stdlib_test ***Failed 83% tests passed, 1 tests failed out of 6 The following tests FAILED: 6 - stdlib_test (Failed) Errors while running CTest make: ** [test] Erro 8 I have written some comments about CTest in: https://sourceforge.net/apps/mediawiki/libposix/index.php?title=How_to_write_tests The only thing that is missing now is the ability of detecting correct standard output on certain tests (like hello world). I have already found a recipe for that (bizarrely, it's not trivial to do that with CTest) and I expect to include the functionality in a few weeks (and also complete the CTest documentation in the wiki). I'll put those in the task page as soon as possible. 2009/7/15 Chris Forbes <ch...@fa...>: > I have no idea about cmake/ctest; I don't use them for my own stuff, since I try to avoid needing a C++ compiler. > Anyway, here's what I use for an embedded project. It's probably horrible in lots of ways, but it allows you to write tests like: > > TEST( my_test_name ) > { > assert( blah ); > } > > or > > TEST( my_other_test, "somestubs.c", "someotherstubs.c" ) > { > assert( blah blah ); > } > > It's just two files: > > $(PROJECT)/gentests.sh: > > #!/bin/bash > > # generate and run test wrappers > # c. forbes (ch...@fa...) > > testsources=`grep -l "TEST(" *.c` > succeeded=0 > failed=0 > > for f in $testsources > do > echo -n "Searching for tests in \`$f\`... " > tests=`grep "TEST(" $f | cut -d'(' -f 2 | cut -d, -f1 | cut -d')' -f1` > echo `echo $tests | wc -w` found. > > for t in $tests > do > deps=`grep "$t" $f | cut -sd, -f2- | cut -d')' -f1` > deps=`echo $deps | sed -e 's/[,\"]//g'` > # echo $t deps: $deps > > testbin=.test-$f-$t > tmpsrc=`mktemp`.c > cat > $tmpsrc << EOT > extern void __test__{{}}( void ); > > int main( int argc, char ** argv ) > { > __test__{{}}(); > return 0; > } > EOT > cat $tmpsrc | sed -e "s/{{}}/$t/g" > $testbin.c > gcc -DTEST_FRAMEWORK -o $testbin.elf -pipe $testbin.c $f $deps > > if ./$testbin.elf; then > # echo SUCCESS > let "succeeded=succeeded+1" > else > # echo FAILED > let "failed=failed+1" > fi > done > done > > rm .test* > if [ $failed = 0 ]; then > echo "$succeeded tests passed." > else > echo "FAILURES!!!" > echo "$failed failed $succeeded ok" > fi > > > > $(INCLUDE)/testfx.h: > > #ifndef _TESTFX_H > #define _TESTFX_H > > #define TEST( test_name, ... )\ > void __test__ ## test_name( void ) > > #endif > > -----Original Message----- > From: Henrique Almeida [mailto:hd...@gm...] > Sent: Thursday, 16 July 2009 11:23 a.m. > To: lib...@li... > Subject: Re: [libposix-development] [PATCH] strncpy implementation and tests > > 2009/7/15 Chris Forbes <ch...@fa...>: >> What are people's thoughts on using a "real" testing framework, to avoid the need to manually specify > > What do you have in mind ? > > things in various places? The required plumbing can be done with just > sh+coreutils. > > But can it be done with CMake/CTest too ? > >> >> -----Original Message----- >> From: Henrique Almeida [mailto:hd...@gm...] >> Sent: Monday, 13 July 2009 4:16 a.m. >> To: lib...@li... >> Subject: Re: [libposix-development] [PATCH] strncpy implementation and tests >> >> I've added a macro, available to the build system to add tests: >> >> add_libposix_test(test_name source1 source2 ...) >> >> CMakeLists.txt now can add tests with a single line rule. >> >> 2009/7/8 Henrique Almeida <hd...@gm...>: >>> 2009/7/4 Henrique Almeida <hd...@gm...>: >>>> >>>> I'll add an article in the wiki explaining the recommended way to >>>> write tests for libposix. >>> >>> A small guide to writing tests for libposix is now available at: >>> >>> https://sourceforge.net/apps/mediawiki/libposix/index.php?title=How_to_write_tests >>> >>>> >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Libposix-development mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libposix-development |
From: Henrique A. <hd...@gm...> - 2009-07-16 03:18:20
|
I've started implementing functions required by bzip2. I'm trying to implement them as simple as possible, with only the functionality required by bzip2. Example functions are fileno() and strerror(). I'll begin to implement open() in the next days. -- Henrique Dante de Almeida hd...@gm... |
From: Henrique A. <hd...@gm...> - 2009-07-16 03:10:30
|
If I understood correctly, CTest is already providing that functionallity. For TEST(), we have add_libposix_test(), which works the same way. The test script is automatically provided by CTest. For example, if I run "make test" on my system I get: Running tests... Start processing tests Test project /home/hdante/código/libposix/libposix.build 1/ 6 Testing puts_hello Passed 2/ 6 Testing hello Passed 3/ 6 Testing printf_scanner Passed 4/ 6 Testing print_parser Passed 5/ 6 Testing strncpy Passed 6/ 6 Testing stdlib_test ***Failed 83% tests passed, 1 tests failed out of 6 The following tests FAILED: 6 - stdlib_test (Failed) Errors while running CTest make: ** [test] Erro 8 I have written some comments about CTest in: https://sourceforge.net/apps/mediawiki/libposix/index.php?title=How_to_write_tests The only thing that is missing now is the ability of detecting correct standard output on certain tests (like hello world). I have already found a recipe for that (bizarrely, it's not trivial to do that with CTest) and I expect to include the functionality in a few weeks (and also complete the CTest documentation in the wiki). I'll put those in the task page as soon as possible. 2009/7/15 Chris Forbes <ch...@fa...>: > I have no idea about cmake/ctest; I don't use them for my own stuff, since I try to avoid needing a C++ compiler. > Anyway, here's what I use for an embedded project. It's probably horrible in lots of ways, but it allows you to write tests like: > > TEST( my_test_name ) > { > assert( blah ); > } > > or > > TEST( my_other_test, "somestubs.c", "someotherstubs.c" ) > { > assert( blah blah ); > } > > It's just two files: > > $(PROJECT)/gentests.sh: > > #!/bin/bash > > # generate and run test wrappers > # c. forbes (ch...@fa...) > > testsources=`grep -l "TEST(" *.c` > succeeded=0 > failed=0 > > for f in $testsources > do > echo -n "Searching for tests in \`$f\`... " > tests=`grep "TEST(" $f | cut -d'(' -f 2 | cut -d, -f1 | cut -d')' -f1` > echo `echo $tests | wc -w` found. > > for t in $tests > do > deps=`grep "$t" $f | cut -sd, -f2- | cut -d')' -f1` > deps=`echo $deps | sed -e 's/[,\"]//g'` > # echo $t deps: $deps > > testbin=.test-$f-$t > tmpsrc=`mktemp`.c > cat > $tmpsrc << EOT > extern void __test__{{}}( void ); > > int main( int argc, char ** argv ) > { > __test__{{}}(); > return 0; > } > EOT > cat $tmpsrc | sed -e "s/{{}}/$t/g" > $testbin.c > gcc -DTEST_FRAMEWORK -o $testbin.elf -pipe $testbin.c $f $deps > > if ./$testbin.elf; then > # echo SUCCESS > let "succeeded=succeeded+1" > else > # echo FAILED > let "failed=failed+1" > fi > done > done > > rm .test* > if [ $failed = 0 ]; then > echo "$succeeded tests passed." > else > echo "FAILURES!!!" > echo "$failed failed $succeeded ok" > fi > > > > $(INCLUDE)/testfx.h: > > #ifndef _TESTFX_H > #define _TESTFX_H > > #define TEST( test_name, ... )\ > void __test__ ## test_name( void ) > > #endif > > -----Original Message----- > From: Henrique Almeida [mailto:hd...@gm...] > Sent: Thursday, 16 July 2009 11:23 a.m. > To: lib...@li... > Subject: Re: [libposix-development] [PATCH] strncpy implementation and tests > > 2009/7/15 Chris Forbes <ch...@fa...>: >> What are people's thoughts on using a "real" testing framework, to avoid the need to manually specify > > What do you have in mind ? > > things in various places? The required plumbing can be done with just > sh+coreutils. > > But can it be done with CMake/CTest too ? > >> >> -----Original Message----- >> From: Henrique Almeida [mailto:hd...@gm...] >> Sent: Monday, 13 July 2009 4:16 a.m. >> To: lib...@li... >> Subject: Re: [libposix-development] [PATCH] strncpy implementation and tests >> >> I've added a macro, available to the build system to add tests: >> >> add_libposix_test(test_name source1 source2 ...) >> >> CMakeLists.txt now can add tests with a single line rule. >> >> 2009/7/8 Henrique Almeida <hd...@gm...>: >>> 2009/7/4 Henrique Almeida <hd...@gm...>: >>>> >>>> I'll add an article in the wiki explaining the recommended way to >>>> write tests for libposix. >>> >>> A small guide to writing tests for libposix is now available at: >>> >>> https://sourceforge.net/apps/mediawiki/libposix/index.php?title=How_to_write_tests >>> >>>> >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... |
From: Chris F. <ch...@fa...> - 2009-07-16 02:46:06
|
I have no idea about cmake/ctest; I don't use them for my own stuff, since I try to avoid needing a C++ compiler. Anyway, here's what I use for an embedded project. It's probably horrible in lots of ways, but it allows you to write tests like: TEST( my_test_name ) { assert( blah ); } or TEST( my_other_test, "somestubs.c", "someotherstubs.c" ) { assert( blah blah ); } It's just two files: $(PROJECT)/gentests.sh: #!/bin/bash # generate and run test wrappers # c. forbes (ch...@fa...) testsources=`grep -l "TEST(" *.c` succeeded=0 failed=0 for f in $testsources do echo -n "Searching for tests in \`$f\`... " tests=`grep "TEST(" $f | cut -d'(' -f 2 | cut -d, -f1 | cut -d')' -f1` echo `echo $tests | wc -w` found. for t in $tests do deps=`grep "$t" $f | cut -sd, -f2- | cut -d')' -f1` deps=`echo $deps | sed -e 's/[,\"]//g'` # echo $t deps: $deps testbin=.test-$f-$t tmpsrc=`mktemp`.c cat > $tmpsrc << EOT extern void __test__{{}}( void ); int main( int argc, char ** argv ) { __test__{{}}(); return 0; } EOT cat $tmpsrc | sed -e "s/{{}}/$t/g" > $testbin.c gcc -DTEST_FRAMEWORK -o $testbin.elf -pipe $testbin.c $f $deps if ./$testbin.elf; then # echo SUCCESS let "succeeded=succeeded+1" else # echo FAILED let "failed=failed+1" fi done done rm .test* if [ $failed = 0 ]; then echo "$succeeded tests passed." else echo "FAILURES!!!" echo "$failed failed $succeeded ok" fi $(INCLUDE)/testfx.h: #ifndef _TESTFX_H #define _TESTFX_H #define TEST( test_name, ... )\ void __test__ ## test_name( void ) #endif -----Original Message----- From: Henrique Almeida [mailto:hd...@gm...] Sent: Thursday, 16 July 2009 11:23 a.m. To: lib...@li... Subject: Re: [libposix-development] [PATCH] strncpy implementation and tests 2009/7/15 Chris Forbes <ch...@fa...>: > What are people's thoughts on using a "real" testing framework, to avoid the need to manually specify What do you have in mind ? things in various places? The required plumbing can be done with just sh+coreutils. But can it be done with CMake/CTest too ? > > -----Original Message----- > From: Henrique Almeida [mailto:hd...@gm...] > Sent: Monday, 13 July 2009 4:16 a.m. > To: lib...@li... > Subject: Re: [libposix-development] [PATCH] strncpy implementation and tests > > I've added a macro, available to the build system to add tests: > > add_libposix_test(test_name source1 source2 ...) > > CMakeLists.txt now can add tests with a single line rule. > > 2009/7/8 Henrique Almeida <hd...@gm...>: >> 2009/7/4 Henrique Almeida <hd...@gm...>: >>> >>> I'll add an article in the wiki explaining the recommended way to >>> write tests for libposix. >> >> A small guide to writing tests for libposix is now available at: >> >> https://sourceforge.net/apps/mediawiki/libposix/index.php?title=How_to_write_tests >> >>> >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Libposix-development mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libposix-development |
From: Henrique A. <hd...@gm...> - 2009-07-15 23:24:35
|
I'll take a look. 2009/7/15 John Haitas <jh...@gm...>: > Trac is good > > On Wed, Jul 15, 2009 at 4:03 PM, Chris Forbes<ch...@fa...> wrote: >> I've used Trac quite successfully. >> >> -----Original Message----- >> From: Henrique Almeida [mailto:hd...@gm...] >> Sent: Wednesday, 15 July 2009 2:41 p.m. >> To: lib...@li... >> Subject: [libposix-development] TaskFreak broken >> >> TaskFreak has been broken for almost one week and I'm unable to edit >> or create tasks. SF folks are not very fast to solve such issues. So, >> I'm thinking about finding another task manager for the project. I'd >> appreciate if anyone can suggest whatever todo, bugzilla, workflow, >> etc. application that could fill the hole. Bonus for applications that >> have the following features: >> >> - task categorization (for Testing, C Development, etc.) >> - task dependencies (depends on, suggests, recommends, etc.) >> - priority indicator (urgent, low, etc.) >> - adding comments to tasks >> - graphical preview of task status (0%, 20% 40%, etc.) >> - full anonymous read-only access (to tasks, category filters, >> comments, etc.) >> - clean, user friendly interface >> >> I'll give you 1 billion dollars if you bring me a task manager with >> all the features above (not really). >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> ------------------------------------------------------------------------ >> ------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> >> vendors submitting new applications to BlackBerry App World(TM) will >> have >> the opportunity to enter the BlackBerry Developer Challenge. See full >> prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >> ------------------------------------------------------------------------------ >> Enter the BlackBerry Developer Challenge >> This is your chance to win up to $100,000 in prizes! For a limited time, >> vendors submitting new applications to BlackBerry App World(TM) will have >> the opportunity to enter the BlackBerry Developer Challenge. See full prize >> details at: http://p.sf.net/sfu/Challenge >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > > > -- > John Haitas > jh...@gm... > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > 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-07-15 23:22:46
|
2009/7/15 Chris Forbes <ch...@fa...>: > What are people's thoughts on using a "real" testing framework, to avoid the need to manually specify What do you have in mind ? things in various places? The required plumbing can be done with just sh+coreutils. But can it be done with CMake/CTest too ? > > -----Original Message----- > From: Henrique Almeida [mailto:hd...@gm...] > Sent: Monday, 13 July 2009 4:16 a.m. > To: lib...@li... > Subject: Re: [libposix-development] [PATCH] strncpy implementation and tests > > I've added a macro, available to the build system to add tests: > > add_libposix_test(test_name source1 source2 ...) > > CMakeLists.txt now can add tests with a single line rule. > > 2009/7/8 Henrique Almeida <hd...@gm...>: >> 2009/7/4 Henrique Almeida <hd...@gm...>: >>> >>> I'll add an article in the wiki explaining the recommended way to >>> write tests for libposix. >> >> A small guide to writing tests for libposix is now available at: >> >> https://sourceforge.net/apps/mediawiki/libposix/index.php?title=How_to_write_tests >> >>> >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... |
From: John H. <jh...@gm...> - 2009-07-15 23:08:20
|
Trac is good On Wed, Jul 15, 2009 at 4:03 PM, Chris Forbes<ch...@fa...> wrote: > I've used Trac quite successfully. > > -----Original Message----- > From: Henrique Almeida [mailto:hd...@gm...] > Sent: Wednesday, 15 July 2009 2:41 p.m. > To: lib...@li... > Subject: [libposix-development] TaskFreak broken > > TaskFreak has been broken for almost one week and I'm unable to edit > or create tasks. SF folks are not very fast to solve such issues. So, > I'm thinking about finding another task manager for the project. I'd > appreciate if anyone can suggest whatever todo, bugzilla, workflow, > etc. application that could fill the hole. Bonus for applications that > have the following features: > > - task categorization (for Testing, C Development, etc.) > - task dependencies (depends on, suggests, recommends, etc.) > - priority indicator (urgent, low, etc.) > - adding comments to tasks > - graphical preview of task status (0%, 20% 40%, etc.) > - full anonymous read-only access (to tasks, category filters, > comments, etc.) > - clean, user friendly interface > > I'll give you 1 billion dollars if you bring me a task manager with > all the features above (not really). > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------ > ------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > > vendors submitting new applications to BlackBerry App World(TM) will > have > the opportunity to enter the BlackBerry Developer Challenge. See full > prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- John Haitas jh...@gm... |
From: Chris F. <ch...@fa...> - 2009-07-15 21:16:34
|
I've used Trac quite successfully. -----Original Message----- From: Henrique Almeida [mailto:hd...@gm...] Sent: Wednesday, 15 July 2009 2:41 p.m. To: lib...@li... Subject: [libposix-development] TaskFreak broken TaskFreak has been broken for almost one week and I'm unable to edit or create tasks. SF folks are not very fast to solve such issues. So, I'm thinking about finding another task manager for the project. I'd appreciate if anyone can suggest whatever todo, bugzilla, workflow, etc. application that could fill the hole. Bonus for applications that have the following features: - task categorization (for Testing, C Development, etc.) - task dependencies (depends on, suggests, recommends, etc.) - priority indicator (urgent, low, etc.) - adding comments to tasks - graphical preview of task status (0%, 20% 40%, etc.) - full anonymous read-only access (to tasks, category filters, comments, etc.) - clean, user friendly interface I'll give you 1 billion dollars if you bring me a task manager with all the features above (not really). -- Henrique Dante de Almeida hd...@gm... ------------------------------------------------------------------------ ------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Libposix-development mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libposix-development |
From: Chris F. <ch...@fa...> - 2009-07-15 21:16:18
|
What are people's thoughts on using a "real" testing framework, to avoid the need to manually specify things in various places? The required plumbing can be done with just sh+coreutils. -----Original Message----- From: Henrique Almeida [mailto:hd...@gm...] Sent: Monday, 13 July 2009 4:16 a.m. To: lib...@li... Subject: Re: [libposix-development] [PATCH] strncpy implementation and tests I've added a macro, available to the build system to add tests: add_libposix_test(test_name source1 source2 ...) CMakeLists.txt now can add tests with a single line rule. 2009/7/8 Henrique Almeida <hd...@gm...>: > 2009/7/4 Henrique Almeida <hd...@gm...>: >> >> I'll add an article in the wiki explaining the recommended way to >> write tests for libposix. > > A small guide to writing tests for libposix is now available at: > > https://sourceforge.net/apps/mediawiki/libposix/index.php?title=How_to_write_tests > >> >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Libposix-development mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libposix-development |
From: Henrique A. <hd...@gm...> - 2009-07-15 02:41:08
|
TaskFreak has been broken for almost one week and I'm unable to edit or create tasks. SF folks are not very fast to solve such issues. So, I'm thinking about finding another task manager for the project. I'd appreciate if anyone can suggest whatever todo, bugzilla, workflow, etc. application that could fill the hole. Bonus for applications that have the following features: - task categorization (for Testing, C Development, etc.) - task dependencies (depends on, suggests, recommends, etc.) - priority indicator (urgent, low, etc.) - adding comments to tasks - graphical preview of task status (0%, 20% 40%, etc.) - full anonymous read-only access (to tasks, category filters, comments, etc.) - clean, user friendly interface I'll give you 1 billion dollars if you bring me a task manager with all the features above (not really). -- Henrique Dante de Almeida hd...@gm... |