libposix-development Mailing List for libposix (Page 6)
Status: Pre-Alpha
Brought to you by:
hdante
Menu
▾
▴
libposix-development — This list is for those who develop or are willing to develop libposix
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(16) |
Jun
(122) |
Jul
(49) |
Aug
(19) |
Sep
(6) |
Oct
(4) |
Nov
(1) |
Dec
|
|---|
|
From: Henrique A. <hd...@gm...> - 2009-06-18 16:18:10
|
Maybe we should choose another application ? 2009/6/18 Jim Meyering <ji...@me...>: > Henrique Almeida wrote: >> I'm building a new libc implementation, called libposix, with a few >> volunteers. We'll begin to use a test driven development approach and >> we're considering GNU coreutils for our initial test case. I'd like to >> know if it's possible to build only small parts of coreutils, instead >> of the full package, during this initial evolution of libposix code. >> Ideally, it would be good if we were able to build only a single tool >> and its dependecies. Also, if that's not possible, maybe you could >> point other applications that would be useful to us. I'm also afraid >> that the configure script would not work with libposix in this stage. >> Is it possible to point out what are the requirements for the >> configure script ? > > The programs in coreutils depend heavily on gnulib. > The parts of gnulib used in coreutils are distributed throughout the > m4/*.m4 files (which are integrated into configure), lib/* files, and > Makefile snippets. The sources and gnulib support are intertwined > enough that separating the src/*.c code from configure-time tests > is likely to be a challenging and subtly error-prone task. > -- Henrique Dante de Almeida hd...@gm... |
|
From: Jim M. <ji...@me...> - 2009-06-18 08:51:10
|
Henrique Almeida wrote: > I'm building a new libc implementation, called libposix, with a few > volunteers. We'll begin to use a test driven development approach and > we're considering GNU coreutils for our initial test case. I'd like to > know if it's possible to build only small parts of coreutils, instead > of the full package, during this initial evolution of libposix code. > Ideally, it would be good if we were able to build only a single tool > and its dependecies. Also, if that's not possible, maybe you could > point other applications that would be useful to us. I'm also afraid > that the configure script would not work with libposix in this stage. > Is it possible to point out what are the requirements for the > configure script ? The programs in coreutils depend heavily on gnulib. The parts of gnulib used in coreutils are distributed throughout the m4/*.m4 files (which are integrated into configure), lib/* files, and Makefile snippets. The sources and gnulib support are intertwined enough that separating the src/*.c code from configure-time tests is likely to be a challenging and subtly error-prone task. |
|
From: Henrique A. <hd...@gm...> - 2009-06-17 23:06:11
|
I've forgot that one, but I've fixed that now. Write access is enabled. 2009/6/9 Henrique Almeida <hd...@gm...>: > > I've just been told that the wiki is not working. I'll try to fix this > tomorrow. I've received a message from Sourceforge saying that soon they'll > better integrate all the third party apps and separate logins will > disappear. > > 2009/6/3 Henrique Almeida <hd...@gm...> >> >> I've added functions starting with U to the wiki. Let's finish this >> task. I'll take the remaining functions after wcsncat. >> >> Those who have already posted their list, please convert it to the >> wiki format and update the wiki. >> >> 2009/6/2 Henrique Almeida <hd...@gm...>: >> > I've created the page. See if it can be edited. >> > >> > >> > https://apps.sourceforge.net/mediawiki/libposix/index.php?title=Function_list >> > >> > 2009/5/31 Henrique Almeida <hd...@gm...>: >> >> While they don't answer, I was able to put you in the "editor" group. >> >> >> >> 2009/5/31 Henrique Almeida <hd...@gm...>: >> >>> I want to give full access to the wiki, but I have no idea how to do >> >>> that. I'll send a message to SF. >> >>> >> >>> 2009/5/31 David Rocamora <dr...@gm...>: >> >>>> Henrique, >> >>>> >> >>>> Can you open up the permissions on the wiki so I can create a page >> >>>> called "function list" or what not. I think we should start with the >> >>>> list we are describing there and have each function link to another >> >>>> wiki page if more description is needed. The wiki seems locked down >> >>>> now so I can't add the page myself. >> >>>> >> >>>> Thanks, >> >>>> Dave >> >>>> >> >>>> On Thu, May 28, 2009 at 3:23 PM, Henrique Almeida <hd...@gm...> >> >>>> wrote: >> >>>>> >> >>>>> >> >>>>> 2009/5/28 Tordek <ke...@gm...>: >> >>>>>> Henrique Almeida wrote: >> >>>>>>> First of all, I hope the message reaches everyone, I'm not sure >> >>>>>>> if >> >>>>>>> the mailing list is working well, so please reply to this post if >> >>>>>>> you've received it. >> >>>>>>> >> >>>>>> >> >>>>>> Yes, it is. >> >>>>> >> >>>>> Nice. >> >>>>> >> >>>>>>> We'll start the project with a simple task. During the project >> >>>>>>> we'll >> >>>>>>> need to mantain the list with the status of each function in the >> >>>>>>> project (that is, if it has been implemented, tested, etc.). >> >>>>>> >> >>>>>> Do we have a wiki, or another place to post this to? A specific >> >>>>>> format? (writing the full description of a function as an example >> >>>>>> would be a great start). >> >>>>>> >> >>>>>> I'd strongly reccomend a wiki, to make it highly navigable >> >>>>>> (categorizing functions per difficulty, and implementedness, for >> >>>>>> one). >> >>>>> >> >>>>> Yes, we definitely need a wiki. SF provides MediaWiki. I have >> >>>>> activated it >> >>>>> on: >> >>>>> >> >>>>> >> >>>>> http://apps.sourceforge.net/mediawiki/libposix/index.php?title=Main_Page >> >>>>> >> >>>>> However, at some moment we'll need to provide a clean and uniform >> >>>>> (and >> >>>>> unique) appearance to the whole site, so we'll need to play with the >> >>>>> CSS >> >>>>> stuff in the wiki. Can you do this ? (btw, we'll need to setup a >> >>>>> task >> >>>>> management page too) >> >>>>> >> >>>>> At the moment, the table needs the following >> >>>>> - function name >> >>>>> - requirement (mandatory or the option group which it belongs) >> >>>>> - whether it's obsolescent or not >> >>>>> - expected difficulty >> >>>>> >> >>>>> The table will grow later, but let's keep it simple for now. For the >> >>>>> functions atoi, crypt and dprintf that would be: >> >>>>> >> >>>>> atoi mandatory (not obsolescent) easy >> >>>>> crypt XSI option (not obsolescent) medium >> >>>>> dprintf mandatory (not obsolescent) hard >> >>>>> >> >>>>> There's another wiki available in SF, called Wikispaces, I don't >> >>>>> know if it >> >>>>> would be better than MediaWiki, though, I've looked at their home >> >>>>> page and >> >>>>> it doesn't seem to be any docs there. >> >>>>> >> >>>>>> >> >>>>>> -- >> >>>>>> Guillermo O. «Tordek» Freschi. Programador, Escritor, Genio >> >>>>>> Maligno. >> >>>>>> http://tordek.com.ar :: http://twitter.com/tordek >> >>>>>> http://www.arcanopedia.com.ar - Juegos de Rol en Argentina >> >>>>>> >> >>>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> Henrique Dante de Almeida >> >>>>> hd...@gm... >> >>>>> >> >>>>> >> >>>>> >> >>>>> ------------------------------------------------------------------------------ >> >>>>> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT >> >>>>> is a gathering of tech-side developers & brand creativity >> >>>>> professionals. >> >>>>> Meet >> >>>>> the minds behind Google Creative Lab, Visual Complexity, Processing, >> >>>>> & >> >>>>> iPhoneDevCamp as they present alongside digital heavyweights like >> >>>>> Barbarian >> >>>>> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com >> >>>>> _______________________________________________ >> >>>>> Libposix-development mailing list >> >>>>> Lib...@li... >> >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >>>>> >> >>>>> >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> Henrique Dante de Almeida >> >>> hd...@gm... >> >>> >> >> >> >> >> >> >> >> -- >> >> Henrique Dante de Almeida >> >> hd...@gm... >> >> >> > >> > >> > >> > -- >> > Henrique Dante de Almeida >> > hd...@gm... >> > >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-17 17:44:46
|
Hello, I'm building a new libc implementation, called libposix, with a few volunteers. We'll begin to use a test driven development approach and we're considering GNU coreutils for our initial test case. I'd like to know if it's possible to build only small parts of coreutils, instead of the full package, during this initial evolution of libposix code. Ideally, it would be good if we were able to build only a single tool and its dependecies. Also, if that's not possible, maybe you could point other applications that would be useful to us. I'm also afraid that the configure script would not work with libposix in this stage. Is it possible to point out what are the requirements for the configure script ? -- Henrique Dante de Almeida hd...@gm... |
|
From: Chris F. <ch...@fa...> - 2009-06-17 05:20:04
|
I'll look into building subsets of coreutils with libposix. At least some of the tools look reasonably self-contained, although the sheer size of the makefiles / configure scripts is a bit daunting :) -- Chris -----Original Message----- From: Henrique Almeida [mailto:hd...@gm...] Sent: Wednesday, 17 June 2009 4:29 p.m. To: lib...@li... Subject: [libposix-development] Installation support and GNU coreutils I've added support for "make install" in libposix. With that we can use libposix as a normal libc so that we can start linking more general software with it. This means we can start "porting" GNU coreutils (or other applications) to libposix. Current installation works as follow: - from libposix directory, cd .. && mkdir libposix.build && cd libposix.build - cmake -D CMAKE_INSTALL_PREFIX=/opt/libposix ../libposix - make - sudo make install - gcc -nostdinc -nostdlib -I /opt/libposix/include -L /opt/libposix/lib -o myapp myapp.c <runtime> -lposix The runtime target is still missing (runtime.o), but it can be done with CMake's add_custom_* functions. Currently, add the runtime sources and includes to <runtime>. We need to find out if it's possible to build small parts of coreutils instead of the whole package. Chris, can you do that ? If it's not possible, we'll need another app. -- Henrique Dante de Almeida hd...@gm... ------------------------------------------------------------------------ ------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Libposix-development mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libposix-development |
|
From: Henrique A. <hd...@gm...> - 2009-06-17 04:28:55
|
I've added support for "make install" in libposix. With that we can use libposix as a normal libc so that we can start linking more general software with it. This means we can start "porting" GNU coreutils (or other applications) to libposix. Current installation works as follow: - from libposix directory, cd .. && mkdir libposix.build && cd libposix.build - cmake -D CMAKE_INSTALL_PREFIX=/opt/libposix ../libposix - make - sudo make install - gcc -nostdinc -nostdlib -I /opt/libposix/include -L /opt/libposix/lib -o myapp myapp.c <runtime> -lposix The runtime target is still missing (runtime.o), but it can be done with CMake's add_custom_* functions. Currently, add the runtime sources and includes to <runtime>. We need to find out if it's possible to build small parts of coreutils instead of the whole package. Chris, can you do that ? If it's not possible, we'll need another app. -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-16 03:17:32
|
I've updated a initial version of a CMakeLists.txt for the project
and it can be compiled with cmake. Instructions follow:
- install cmake ("sudo apt-get install cmake" in Ubuntu)
- from "libposix" directory, cd .. && mkdir libposix.build && cd libposix.build
- cmake ../libposix
- make
Please test. It should work on all targets. Immediate TODO list follows:
- add a target for runtime (runtime.o)
- remove hardcoded path (RPATH) for libposix in "hello"
- improve system/architecture detection to map to "platform sets"
(I'll describe those later)
--
Henrique Dante de Almeida
hd...@gm...
|
|
From: Henrique A. <hd...@gm...> - 2009-06-14 21:03:52
|
I'm not attacking anyone. And sorry, I won't keep arguing, specially when someone starts assuming I've said things that I didn't. The project will get it right, the sooner the better, but it doesn't really matter when. 2009/6/14 Andreas Krennmair <akr...@go...>: > Henrique, > > Open source projects simply don't work that way. You attacked me for > not immediately implementing the rules of architecture independence. > Why can't you simply fix that when merging the commits? As I already > wrote, my changes are x86_64 specific, as this is pretty much the only > platform that I have available. > > In the case of libposix, you have the real world (Linux) and the > standard world (POSIX.1-2008). Both world differ, but in order to > implement the standard, you need to interconnect with the real world, > and you cannot completely ignore it. Finding a practical way to > interconnect these two worlds is not something that can be planned > easily, and there will be changes to it, at least once more than > planned. And you require me to "get it right" up-front?! That's just > ridiculous. Software development has a tool to remedy such problems, > it is called "refactoring". You're going to need it in the future, > even with your strict separation of "master" and "broken" branches. > > Having said that, I think that you, taking pride in your up-front > planning efforts without any practical need (how many other developers > contribute code, too?), have no clue how open source projects are > managed and why people take part in open source projects. It's not my > job to work on libposix, I purely do this for fun and joy, and having > to obey to all the rules that you make up in order to organize things > (organize what? who? there is practically nothing and nobody that > needs to be managed and/or organized yet!) really takes away the fun > from the project, the very essence of why I have contributed so far. > > Regards, > Andreas > > On Sun, Jun 14, 2009 at 8:08 PM, Henrique Almeida<hd...@gm...> wrote: >> I don't think the code rules are overly stringent. The method to deal >> with real world implementations was described in the last post (so I >> don't need to repeat it here). I don't think organizing things is >> ridiculous either. Actually, I'm very proud of doing that way. >> >> See you, >> >> 2009/6/14 Andreas Krennmair <akr...@go...>: >>> Linux is not a standard, but Linux is real! If you want to support >>> certain system calls on Linux, you must adhere to Linux's data >>> structures. Or are you trying to suggest that I should write a wrapper >>> around such things that map the Linux data structures to data >>> structures that adhere to POSIX.1-2008 and POSIX.1-2008 only? That >>> would be just outright crazy. >>> >>> Anyway, your tight restrictions on the code and all your fighting >>> about the confrontation with real-world conditions really took my last >>> motivation to contribute my code. Apparently, working on the code >>> itself for this project is fun, and I will keep developing in my own >>> development branch, but don't expect me to report any improvements or >>> changes that I made here. >>> >>> Good luck to you and all the other contributing C developers, low >>> level developers, testers, web designers, web developers, web >>> editors/bloggers/"PR guys", build system developers/port maintainers, >>> performance developers, roadmap managers and code reviewers. With more >>> stringent code conformity rules and tighter project roles, you will >>> surely make it! >>> >>> Best regards, >>> Andreas >>> >>> On Sat, Jun 13, 2009 at 11:14 PM, Henrique Almeida<hd...@gm...> wrote: >>>> No, that won't do. Submitted code must follow the standard (or must >>>> go to system specific directories). It doesn't make sense for the >>>> project otherwise. >>>> >>>> - Code that is contributed must be written for the standard. Linux is >>>> not a standard. (for example, sigval_t is not defined in the standard, >>>> sigval is, __band_t is not defined either). >>>> - System specific code that must go to the system directory. They >>>> always need a reference that proves that they're necessary. >>>> - Code that is copied from other libraries must have original >>>> author's notice, so that it can be tagged as derived work (and the >>>> license must allow that). >>>> >>>> 2009/6/13 Andreas Krennmair <akr...@go...>: >>>>> Henrique, >>>>> >>>>> I'm not pulling the struct definition out of my a**, Linux is the way >>>>> it is (especially its kernel data structures), and there's nothing >>>>> that can be changed about it from my side. If this is unacceptable, >>>>> well, then I can't help you. Take the code or leave it, it's all your >>>>> decision. Having to vindicate every single line of code that I >>>>> contribute isn't exactly something that makes me eager to contribute >>>>> more code. >>>>> >>>>> Best regards, >>>>> Andreas >>>>> >>>>> On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote: >>>>>> Comments for commit: >>>>>> >>>>>> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system >>>>>> calls (including auto-generator script). >>>>>> >>>>>> signal.h: >>>>>> - the "include" files can't contain conditional code (_WORDSIZE), >>>>>> move signal.h to system specific directories (or add an #include >>>>>> <arch_signal.h>) >>>>>> stat.h: >>>>>> - __pad0, __st_ino, etc. where did those come from ? >>>>>> - can't have __attribute__ extension in "include" directory (where >>>>>> did those come from ?) >>>>>> - sigval_t this doesn't exist in the standard >>>>>> >>>>>> Are you copying this from an older implementation ? There are too many >>>>>> unexpected features in this patch. I need to understand what's this >>>>>> all about before I continue reading the patches. I can't spend time >>>>>> verifying that non standard code is being submitted, this has to be >>>>>> done by the contributor. >>>>>> >>>>>> 2009/6/12 Henrique Almeida <hd...@gm...>: >>>>>>> Comments for commit: >>>>>>> >>>>>>> 9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build. >>>>>>> >>>>>>> - uncomment #ifdef in syscall_nums.h >>>>>>> - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi >>>>>>> >>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>> Broken branch updated up to 2009-06-05 >>>>>>>> >>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>> Comments for commit: >>>>>>>>> >>>>>>>>> 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() >>>>>>>>> including unit tests. >>>>>>>>> >>>>>>>>> on strrchr.c, '\0' must be considered part of the string, fix both >>>>>>>>> the implementation and test >>>>>>>>> >>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>>> Comments for commit: >>>>>>>>>> >>>>>>>>>> d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already >>>>>>>>>> implemented str* functions. >>>>>>>>>> >>>>>>>>>> - remove test prefix from file names >>>>>>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is >>>>>>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 >>>>>>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX >>>>>>>>>> - add test coverage to strcpy: out of bound writes (both sides) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>>>> Comments for commit: >>>>>>>>>>> >>>>>>>>>>> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >>>>>>>>>>> >>>>>>>>>>> - sys/mman.h >>>>>>>>>>> - the PROT_* macros are system dependent (they depend on the kernel used). >>>>>>>>>>> mman.h should be moved to the system directory. Also, the reference for >>>>>>>>>>> the values for linux are missing. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>>>>> >>>>>>>>>>>> I have done a git pull here and there are individual commits. I think I >>>>>>>>>>>> haven't noticed them earlier. I'll begin to read each of them. >>>>>>>>>>>> >>>>>>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>>>>>>>>>>> >>>>>>>>>>>>> The problem was that the merge was condensed into a single commit (or >>>>>>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later, >>>>>>>>>>>>> but at the moment there are some merge issues to resolve. >>>>>>>>>>>>> >>>>>>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>>>>>>>>>>> >>>>>>>>>>>>>> If there are differences, you always need an extra merge commit, as far >>>>>>>>>>>>>> as I understand. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>>>>>>>>>>> my branch: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>>>>>>>>>>> Merge: 1faac1a... 05b56ea... >>>>>>>>>>>>>>> Author: Henrique <hd...@us...> >>>>>>>>>>>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> * git://github.com/akrennmair/libposix: >>>>>>>>>>>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>>>>>>>>>>> implemented strrchr() including unit tests. >>>>>>>>>>>>>>> fixed build dependencies for tests. >>>>>>>>>>>>>>> added unit tests for already implemented str* functions. >>>>>>>>>>>>>>> added mmap and munmap. >>>>>>>>>>>>>>> added simple unit tests for already implemented mem* functions. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Is there a way to fix this ? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Ok, good idea, git branches rock ! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hello everybody, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>>>>>>>>>>> official libposix repository by executing >>>>>>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>>>>>>>>>>> easier to reintegrate with the official development line. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>>>>>>>>>>> two. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>> Andreas >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>>>>>>> latest >>>>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>>>>>> hd...@gm... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>>>>> hd...@gm... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>>>>> latest >>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest >>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>>> hd...@gm... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>> hd...@gm... >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>> hd...@gm... >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>> hd...@gm... >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Henrique Dante de Almeida >>>>>>>>> hd...@gm... >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Henrique Dante de Almeida >>>>>>>> hd...@gm... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Crystal Reports - New Free Runtime and 30 Day Trial >>>>>> Check out the new simplified licensing option that enables unlimited >>>>>> royalty-free distribution of the report engine for externally facing >>>>>> server and web deployment. >>>>>> http://p.sf.net/sfu/businessobjects >>>>>> _______________________________________________ >>>>>> Libposix-development mailing list >>>>>> Lib...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Crystal Reports - New Free Runtime and 30 Day Trial >>>>> Check out the new simplified licensing option that enables unlimited >>>>> royalty-free distribution of the report engine for externally facing >>>>> server and web deployment. >>>>> http://p.sf.net/sfu/businessobjects >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>>> ------------------------------------------------------------------------------ >>>> Crystal Reports - New Free Runtime and 30 Day Trial >>>> Check out the new simplified licensing option that enables unlimited >>>> royalty-free distribution of the report engine for externally facing >>>> server and web deployment. >>>> http://p.sf.net/sfu/businessobjects >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensing option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-14 20:10:07
|
Henrique, Open source projects simply don't work that way. You attacked me for not immediately implementing the rules of architecture independence. Why can't you simply fix that when merging the commits? As I already wrote, my changes are x86_64 specific, as this is pretty much the only platform that I have available. In the case of libposix, you have the real world (Linux) and the standard world (POSIX.1-2008). Both world differ, but in order to implement the standard, you need to interconnect with the real world, and you cannot completely ignore it. Finding a practical way to interconnect these two worlds is not something that can be planned easily, and there will be changes to it, at least once more than planned. And you require me to "get it right" up-front?! That's just ridiculous. Software development has a tool to remedy such problems, it is called "refactoring". You're going to need it in the future, even with your strict separation of "master" and "broken" branches. Having said that, I think that you, taking pride in your up-front planning efforts without any practical need (how many other developers contribute code, too?), have no clue how open source projects are managed and why people take part in open source projects. It's not my job to work on libposix, I purely do this for fun and joy, and having to obey to all the rules that you make up in order to organize things (organize what? who? there is practically nothing and nobody that needs to be managed and/or organized yet!) really takes away the fun from the project, the very essence of why I have contributed so far. Regards, Andreas On Sun, Jun 14, 2009 at 8:08 PM, Henrique Almeida<hd...@gm...> wrote: > I don't think the code rules are overly stringent. The method to deal > with real world implementations was described in the last post (so I > don't need to repeat it here). I don't think organizing things is > ridiculous either. Actually, I'm very proud of doing that way. > > See you, > > 2009/6/14 Andreas Krennmair <akr...@go...>: >> Linux is not a standard, but Linux is real! If you want to support >> certain system calls on Linux, you must adhere to Linux's data >> structures. Or are you trying to suggest that I should write a wrapper >> around such things that map the Linux data structures to data >> structures that adhere to POSIX.1-2008 and POSIX.1-2008 only? That >> would be just outright crazy. >> >> Anyway, your tight restrictions on the code and all your fighting >> about the confrontation with real-world conditions really took my last >> motivation to contribute my code. Apparently, working on the code >> itself for this project is fun, and I will keep developing in my own >> development branch, but don't expect me to report any improvements or >> changes that I made here. >> >> Good luck to you and all the other contributing C developers, low >> level developers, testers, web designers, web developers, web >> editors/bloggers/"PR guys", build system developers/port maintainers, >> performance developers, roadmap managers and code reviewers. With more >> stringent code conformity rules and tighter project roles, you will >> surely make it! >> >> Best regards, >> Andreas >> >> On Sat, Jun 13, 2009 at 11:14 PM, Henrique Almeida<hd...@gm...> wrote: >>> No, that won't do. Submitted code must follow the standard (or must >>> go to system specific directories). It doesn't make sense for the >>> project otherwise. >>> >>> - Code that is contributed must be written for the standard. Linux is >>> not a standard. (for example, sigval_t is not defined in the standard, >>> sigval is, __band_t is not defined either). >>> - System specific code that must go to the system directory. They >>> always need a reference that proves that they're necessary. >>> - Code that is copied from other libraries must have original >>> author's notice, so that it can be tagged as derived work (and the >>> license must allow that). >>> >>> 2009/6/13 Andreas Krennmair <akr...@go...>: >>>> Henrique, >>>> >>>> I'm not pulling the struct definition out of my a**, Linux is the way >>>> it is (especially its kernel data structures), and there's nothing >>>> that can be changed about it from my side. If this is unacceptable, >>>> well, then I can't help you. Take the code or leave it, it's all your >>>> decision. Having to vindicate every single line of code that I >>>> contribute isn't exactly something that makes me eager to contribute >>>> more code. >>>> >>>> Best regards, >>>> Andreas >>>> >>>> On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote: >>>>> Comments for commit: >>>>> >>>>> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system >>>>> calls (including auto-generator script). >>>>> >>>>> signal.h: >>>>> - the "include" files can't contain conditional code (_WORDSIZE), >>>>> move signal.h to system specific directories (or add an #include >>>>> <arch_signal.h>) >>>>> stat.h: >>>>> - __pad0, __st_ino, etc. where did those come from ? >>>>> - can't have __attribute__ extension in "include" directory (where >>>>> did those come from ?) >>>>> - sigval_t this doesn't exist in the standard >>>>> >>>>> Are you copying this from an older implementation ? There are too many >>>>> unexpected features in this patch. I need to understand what's this >>>>> all about before I continue reading the patches. I can't spend time >>>>> verifying that non standard code is being submitted, this has to be >>>>> done by the contributor. >>>>> >>>>> 2009/6/12 Henrique Almeida <hd...@gm...>: >>>>>> Comments for commit: >>>>>> >>>>>> 9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build. >>>>>> >>>>>> - uncomment #ifdef in syscall_nums.h >>>>>> - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi >>>>>> >>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>> Broken branch updated up to 2009-06-05 >>>>>>> >>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>> Comments for commit: >>>>>>>> >>>>>>>> 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() >>>>>>>> including unit tests. >>>>>>>> >>>>>>>> on strrchr.c, '\0' must be considered part of the string, fix both >>>>>>>> the implementation and test >>>>>>>> >>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>> Comments for commit: >>>>>>>>> >>>>>>>>> d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already >>>>>>>>> implemented str* functions. >>>>>>>>> >>>>>>>>> - remove test prefix from file names >>>>>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is >>>>>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 >>>>>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX >>>>>>>>> - add test coverage to strcpy: out of bound writes (both sides) >>>>>>>>> >>>>>>>>> >>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>>> Comments for commit: >>>>>>>>>> >>>>>>>>>> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >>>>>>>>>> >>>>>>>>>> - sys/mman.h >>>>>>>>>> - the PROT_* macros are system dependent (they depend on the kernel used). >>>>>>>>>> mman.h should be moved to the system directory. Also, the reference for >>>>>>>>>> the values for linux are missing. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>>>> >>>>>>>>>>> I have done a git pull here and there are individual commits. I think I >>>>>>>>>>> haven't noticed them earlier. I'll begin to read each of them. >>>>>>>>>>> >>>>>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>>>>>>>>>> >>>>>>>>>>>> The problem was that the merge was condensed into a single commit (or >>>>>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later, >>>>>>>>>>>> but at the moment there are some merge issues to resolve. >>>>>>>>>>>> >>>>>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>>>>>>>>>> >>>>>>>>>>>>> If there are differences, you always need an extra merge commit, as far >>>>>>>>>>>>> as I understand. >>>>>>>>>>>>> >>>>>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>>>>>>>>>> my branch: >>>>>>>>>>>>>> >>>>>>>>>>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>>>>>>>>>> Merge: 1faac1a... 05b56ea... >>>>>>>>>>>>>> Author: Henrique <hd...@us...> >>>>>>>>>>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>>>>>>>>>> >>>>>>>>>>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>>>>>>>>>> >>>>>>>>>>>>>> * git://github.com/akrennmair/libposix: >>>>>>>>>>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>>>>>>>>>> implemented strrchr() including unit tests. >>>>>>>>>>>>>> fixed build dependencies for tests. >>>>>>>>>>>>>> added unit tests for already implemented str* functions. >>>>>>>>>>>>>> added mmap and munmap. >>>>>>>>>>>>>> added simple unit tests for already implemented mem* functions. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Is there a way to fix this ? >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Ok, good idea, git branches rock ! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hello everybody, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>>>>>>>>>> official libposix repository by executing >>>>>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>>>>>>>>>> easier to reintegrate with the official development line. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>>>>>>>>>> two. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>> Andreas >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>>>>>> latest >>>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>>>>> hd...@gm... >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>>>> hd...@gm... >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>>>> latest >>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest >>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>> hd...@gm... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>> hd...@gm... >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>> hd...@gm... >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Henrique Dante de Almeida >>>>>>>>> hd...@gm... >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Henrique Dante de Almeida >>>>>>>> hd...@gm... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Crystal Reports - New Free Runtime and 30 Day Trial >>>>> Check out the new simplified licensing option that enables unlimited >>>>> royalty-free distribution of the report engine for externally facing >>>>> server and web deployment. >>>>> http://p.sf.net/sfu/businessobjects >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Crystal Reports - New Free Runtime and 30 Day Trial >>>> Check out the new simplified licensing option that enables unlimited >>>> royalty-free distribution of the report engine for externally facing >>>> server and web deployment. >>>> http://p.sf.net/sfu/businessobjects >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensing option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > |
|
From: Henrique A. <hd...@gm...> - 2009-06-14 18:08:34
|
I don't think the code rules are overly stringent. The method to deal with real world implementations was described in the last post (so I don't need to repeat it here). I don't think organizing things is ridiculous either. Actually, I'm very proud of doing that way. See you, 2009/6/14 Andreas Krennmair <akr...@go...>: > Linux is not a standard, but Linux is real! If you want to support > certain system calls on Linux, you must adhere to Linux's data > structures. Or are you trying to suggest that I should write a wrapper > around such things that map the Linux data structures to data > structures that adhere to POSIX.1-2008 and POSIX.1-2008 only? That > would be just outright crazy. > > Anyway, your tight restrictions on the code and all your fighting > about the confrontation with real-world conditions really took my last > motivation to contribute my code. Apparently, working on the code > itself for this project is fun, and I will keep developing in my own > development branch, but don't expect me to report any improvements or > changes that I made here. > > Good luck to you and all the other contributing C developers, low > level developers, testers, web designers, web developers, web > editors/bloggers/"PR guys", build system developers/port maintainers, > performance developers, roadmap managers and code reviewers. With more > stringent code conformity rules and tighter project roles, you will > surely make it! > > Best regards, > Andreas > > On Sat, Jun 13, 2009 at 11:14 PM, Henrique Almeida<hd...@gm...> wrote: >> No, that won't do. Submitted code must follow the standard (or must >> go to system specific directories). It doesn't make sense for the >> project otherwise. >> >> - Code that is contributed must be written for the standard. Linux is >> not a standard. (for example, sigval_t is not defined in the standard, >> sigval is, __band_t is not defined either). >> - System specific code that must go to the system directory. They >> always need a reference that proves that they're necessary. >> - Code that is copied from other libraries must have original >> author's notice, so that it can be tagged as derived work (and the >> license must allow that). >> >> 2009/6/13 Andreas Krennmair <akr...@go...>: >>> Henrique, >>> >>> I'm not pulling the struct definition out of my a**, Linux is the way >>> it is (especially its kernel data structures), and there's nothing >>> that can be changed about it from my side. If this is unacceptable, >>> well, then I can't help you. Take the code or leave it, it's all your >>> decision. Having to vindicate every single line of code that I >>> contribute isn't exactly something that makes me eager to contribute >>> more code. >>> >>> Best regards, >>> Andreas >>> >>> On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote: >>>> Comments for commit: >>>> >>>> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system >>>> calls (including auto-generator script). >>>> >>>> signal.h: >>>> - the "include" files can't contain conditional code (_WORDSIZE), >>>> move signal.h to system specific directories (or add an #include >>>> <arch_signal.h>) >>>> stat.h: >>>> - __pad0, __st_ino, etc. where did those come from ? >>>> - can't have __attribute__ extension in "include" directory (where >>>> did those come from ?) >>>> - sigval_t this doesn't exist in the standard >>>> >>>> Are you copying this from an older implementation ? There are too many >>>> unexpected features in this patch. I need to understand what's this >>>> all about before I continue reading the patches. I can't spend time >>>> verifying that non standard code is being submitted, this has to be >>>> done by the contributor. >>>> >>>> 2009/6/12 Henrique Almeida <hd...@gm...>: >>>>> Comments for commit: >>>>> >>>>> 9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build. >>>>> >>>>> - uncomment #ifdef in syscall_nums.h >>>>> - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi >>>>> >>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>> Broken branch updated up to 2009-06-05 >>>>>> >>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>> Comments for commit: >>>>>>> >>>>>>> 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() >>>>>>> including unit tests. >>>>>>> >>>>>>> on strrchr.c, '\0' must be considered part of the string, fix both >>>>>>> the implementation and test >>>>>>> >>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>> Comments for commit: >>>>>>>> >>>>>>>> d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already >>>>>>>> implemented str* functions. >>>>>>>> >>>>>>>> - remove test prefix from file names >>>>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is >>>>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 >>>>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX >>>>>>>> - add test coverage to strcpy: out of bound writes (both sides) >>>>>>>> >>>>>>>> >>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>> Comments for commit: >>>>>>>>> >>>>>>>>> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >>>>>>>>> >>>>>>>>> - sys/mman.h >>>>>>>>> - the PROT_* macros are system dependent (they depend on the kernel used). >>>>>>>>> mman.h should be moved to the system directory. Also, the reference for >>>>>>>>> the values for linux are missing. >>>>>>>>> >>>>>>>>> >>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>>> >>>>>>>>>> I have done a git pull here and there are individual commits. I think I >>>>>>>>>> haven't noticed them earlier. I'll begin to read each of them. >>>>>>>>>> >>>>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>>>>>>>>> >>>>>>>>>>> The problem was that the merge was condensed into a single commit (or >>>>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later, >>>>>>>>>>> but at the moment there are some merge issues to resolve. >>>>>>>>>>> >>>>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>>>>>>>>> >>>>>>>>>>>> If there are differences, you always need an extra merge commit, as far >>>>>>>>>>>> as I understand. >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>>>>>>>>> my branch: >>>>>>>>>>>>> >>>>>>>>>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>>>>>>>>> Merge: 1faac1a... 05b56ea... >>>>>>>>>>>>> Author: Henrique <hd...@us...> >>>>>>>>>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>>>>>>>>> >>>>>>>>>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>>>>>>>>> >>>>>>>>>>>>> * git://github.com/akrennmair/libposix: >>>>>>>>>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>>>>>>>>> implemented strrchr() including unit tests. >>>>>>>>>>>>> fixed build dependencies for tests. >>>>>>>>>>>>> added unit tests for already implemented str* functions. >>>>>>>>>>>>> added mmap and munmap. >>>>>>>>>>>>> added simple unit tests for already implemented mem* functions. >>>>>>>>>>>>> >>>>>>>>>>>>> Is there a way to fix this ? >>>>>>>>>>>>> >>>>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Ok, good idea, git branches rock ! >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hello everybody, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>>>>>>>>> official libposix repository by executing >>>>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>>>>>>>>> easier to reintegrate with the official development line. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>>>>>>>>> two. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>> Andreas >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>>>>> latest >>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>>>> hd...@gm... >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>>> hd...@gm... >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>>> latest >>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest >>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>> Lib...@li... >>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>> hd...@gm... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>> hd...@gm... >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Henrique Dante de Almeida >>>>>>>>> hd...@gm... >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Henrique Dante de Almeida >>>>>>>> hd...@gm... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>>> ------------------------------------------------------------------------------ >>>> Crystal Reports - New Free Runtime and 30 Day Trial >>>> Check out the new simplified licensing option that enables unlimited >>>> royalty-free distribution of the report engine for externally facing >>>> server and web deployment. >>>> http://p.sf.net/sfu/businessobjects >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensing option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-14 09:34:31
|
Linux is not a standard, but Linux is real! If you want to support certain system calls on Linux, you must adhere to Linux's data structures. Or are you trying to suggest that I should write a wrapper around such things that map the Linux data structures to data structures that adhere to POSIX.1-2008 and POSIX.1-2008 only? That would be just outright crazy. Anyway, your tight restrictions on the code and all your fighting about the confrontation with real-world conditions really took my last motivation to contribute my code. Apparently, working on the code itself for this project is fun, and I will keep developing in my own development branch, but don't expect me to report any improvements or changes that I made here. Good luck to you and all the other contributing C developers, low level developers, testers, web designers, web developers, web editors/bloggers/"PR guys", build system developers/port maintainers, performance developers, roadmap managers and code reviewers. With more stringent code conformity rules and tighter project roles, you will surely make it! Best regards, Andreas On Sat, Jun 13, 2009 at 11:14 PM, Henrique Almeida<hd...@gm...> wrote: > No, that won't do. Submitted code must follow the standard (or must > go to system specific directories). It doesn't make sense for the > project otherwise. > > - Code that is contributed must be written for the standard. Linux is > not a standard. (for example, sigval_t is not defined in the standard, > sigval is, __band_t is not defined either). > - System specific code that must go to the system directory. They > always need a reference that proves that they're necessary. > - Code that is copied from other libraries must have original > author's notice, so that it can be tagged as derived work (and the > license must allow that). > > 2009/6/13 Andreas Krennmair <akr...@go...>: >> Henrique, >> >> I'm not pulling the struct definition out of my a**, Linux is the way >> it is (especially its kernel data structures), and there's nothing >> that can be changed about it from my side. If this is unacceptable, >> well, then I can't help you. Take the code or leave it, it's all your >> decision. Having to vindicate every single line of code that I >> contribute isn't exactly something that makes me eager to contribute >> more code. >> >> Best regards, >> Andreas >> >> On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote: >>> Comments for commit: >>> >>> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system >>> calls (including auto-generator script). >>> >>> signal.h: >>> - the "include" files can't contain conditional code (_WORDSIZE), >>> move signal.h to system specific directories (or add an #include >>> <arch_signal.h>) >>> stat.h: >>> - __pad0, __st_ino, etc. where did those come from ? >>> - can't have __attribute__ extension in "include" directory (where >>> did those come from ?) >>> - sigval_t this doesn't exist in the standard >>> >>> Are you copying this from an older implementation ? There are too many >>> unexpected features in this patch. I need to understand what's this >>> all about before I continue reading the patches. I can't spend time >>> verifying that non standard code is being submitted, this has to be >>> done by the contributor. >>> >>> 2009/6/12 Henrique Almeida <hd...@gm...>: >>>> Comments for commit: >>>> >>>> 9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build. >>>> >>>> - uncomment #ifdef in syscall_nums.h >>>> - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi >>>> >>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>> Broken branch updated up to 2009-06-05 >>>>> >>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>> Comments for commit: >>>>>> >>>>>> 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() >>>>>> including unit tests. >>>>>> >>>>>> on strrchr.c, '\0' must be considered part of the string, fix both >>>>>> the implementation and test >>>>>> >>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>> Comments for commit: >>>>>>> >>>>>>> d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already >>>>>>> implemented str* functions. >>>>>>> >>>>>>> - remove test prefix from file names >>>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is >>>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 >>>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX >>>>>>> - add test coverage to strcpy: out of bound writes (both sides) >>>>>>> >>>>>>> >>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>> Comments for commit: >>>>>>>> >>>>>>>> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >>>>>>>> >>>>>>>> - sys/mman.h >>>>>>>> - the PROT_* macros are system dependent (they depend on the kernel used). >>>>>>>> mman.h should be moved to the system directory. Also, the reference for >>>>>>>> the values for linux are missing. >>>>>>>> >>>>>>>> >>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>>> >>>>>>>>> I have done a git pull here and there are individual commits. I think I >>>>>>>>> haven't noticed them earlier. I'll begin to read each of them. >>>>>>>>> >>>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>>>>>>>> >>>>>>>>>> The problem was that the merge was condensed into a single commit (or >>>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later, >>>>>>>>>> but at the moment there are some merge issues to resolve. >>>>>>>>>> >>>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>>>>>>>> >>>>>>>>>>> If there are differences, you always need an extra merge commit, as far >>>>>>>>>>> as I understand. >>>>>>>>>>> >>>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>>>>>>>> my branch: >>>>>>>>>>>> >>>>>>>>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>>>>>>>> Merge: 1faac1a... 05b56ea... >>>>>>>>>>>> Author: Henrique <hd...@us...> >>>>>>>>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>>>>>>>> >>>>>>>>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>>>>>>>> >>>>>>>>>>>> * git://github.com/akrennmair/libposix: >>>>>>>>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>>>>>>>> implemented strrchr() including unit tests. >>>>>>>>>>>> fixed build dependencies for tests. >>>>>>>>>>>> added unit tests for already implemented str* functions. >>>>>>>>>>>> added mmap and munmap. >>>>>>>>>>>> added simple unit tests for already implemented mem* functions. >>>>>>>>>>>> >>>>>>>>>>>> Is there a way to fix this ? >>>>>>>>>>>> >>>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>>>>>>>> >>>>>>>>>>>>> Ok, good idea, git branches rock ! >>>>>>>>>>>>> >>>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hello everybody, >>>>>>>>>>>>>> >>>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>>>>>>>> official libposix repository by executing >>>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>>>>>>>> easier to reintegrate with the official development line. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>>>>>>>> two. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>> Andreas >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>>>> latest >>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>>> hd...@gm... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>> hd...@gm... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>> latest >>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>> Lib...@li... >>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest >>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>> Lib...@li... >>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>> hd...@gm... >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Henrique Dante de Almeida >>>>>>>>> hd...@gm... >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Henrique Dante de Almeida >>>>>>>> hd...@gm... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensing option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > |
|
From: Henrique A. <hd...@gm...> - 2009-06-13 21:14:05
|
No, that won't do. Submitted code must follow the standard (or must go to system specific directories). It doesn't make sense for the project otherwise. - Code that is contributed must be written for the standard. Linux is not a standard. (for example, sigval_t is not defined in the standard, sigval is, __band_t is not defined either). - System specific code that must go to the system directory. They always need a reference that proves that they're necessary. - Code that is copied from other libraries must have original author's notice, so that it can be tagged as derived work (and the license must allow that). 2009/6/13 Andreas Krennmair <akr...@go...>: > Henrique, > > I'm not pulling the struct definition out of my a**, Linux is the way > it is (especially its kernel data structures), and there's nothing > that can be changed about it from my side. If this is unacceptable, > well, then I can't help you. Take the code or leave it, it's all your > decision. Having to vindicate every single line of code that I > contribute isn't exactly something that makes me eager to contribute > more code. > > Best regards, > Andreas > > On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote: >> Comments for commit: >> >> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system >> calls (including auto-generator script). >> >> signal.h: >> - the "include" files can't contain conditional code (_WORDSIZE), >> move signal.h to system specific directories (or add an #include >> <arch_signal.h>) >> stat.h: >> - __pad0, __st_ino, etc. where did those come from ? >> - can't have __attribute__ extension in "include" directory (where >> did those come from ?) >> - sigval_t this doesn't exist in the standard >> >> Are you copying this from an older implementation ? There are too many >> unexpected features in this patch. I need to understand what's this >> all about before I continue reading the patches. I can't spend time >> verifying that non standard code is being submitted, this has to be >> done by the contributor. >> >> 2009/6/12 Henrique Almeida <hd...@gm...>: >>> Comments for commit: >>> >>> 9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build. >>> >>> - uncomment #ifdef in syscall_nums.h >>> - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi >>> >>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>> Broken branch updated up to 2009-06-05 >>>> >>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>> Comments for commit: >>>>> >>>>> 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() >>>>> including unit tests. >>>>> >>>>> on strrchr.c, '\0' must be considered part of the string, fix both >>>>> the implementation and test >>>>> >>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>> Comments for commit: >>>>>> >>>>>> d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already >>>>>> implemented str* functions. >>>>>> >>>>>> - remove test prefix from file names >>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is >>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 >>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX >>>>>> - add test coverage to strcpy: out of bound writes (both sides) >>>>>> >>>>>> >>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>> Comments for commit: >>>>>>> >>>>>>> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >>>>>>> >>>>>>> - sys/mman.h >>>>>>> - the PROT_* macros are system dependent (they depend on the kernel used). >>>>>>> mman.h should be moved to the system directory. Also, the reference for >>>>>>> the values for linux are missing. >>>>>>> >>>>>>> >>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>>> >>>>>>>> I have done a git pull here and there are individual commits. I think I >>>>>>>> haven't noticed them earlier. I'll begin to read each of them. >>>>>>>> >>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>>>>>>> >>>>>>>>> The problem was that the merge was condensed into a single commit (or >>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later, >>>>>>>>> but at the moment there are some merge issues to resolve. >>>>>>>>> >>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>>>>>>> >>>>>>>>>> If there are differences, you always need an extra merge commit, as far >>>>>>>>>> as I understand. >>>>>>>>>> >>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>>>>>>> my branch: >>>>>>>>>>> >>>>>>>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>>>>>>> Merge: 1faac1a... 05b56ea... >>>>>>>>>>> Author: Henrique <hd...@us...> >>>>>>>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>>>>>>> >>>>>>>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>>>>>>> >>>>>>>>>>> * git://github.com/akrennmair/libposix: >>>>>>>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>>>>>>> implemented strrchr() including unit tests. >>>>>>>>>>> fixed build dependencies for tests. >>>>>>>>>>> added unit tests for already implemented str* functions. >>>>>>>>>>> added mmap and munmap. >>>>>>>>>>> added simple unit tests for already implemented mem* functions. >>>>>>>>>>> >>>>>>>>>>> Is there a way to fix this ? >>>>>>>>>>> >>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>>>>>>> >>>>>>>>>>>> Ok, good idea, git branches rock ! >>>>>>>>>>>> >>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>>>>>>> >>>>>>>>>>>>> Hello everybody, >>>>>>>>>>>>> >>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>>>>>>> official libposix repository by executing >>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>>>>>>> easier to reintegrate with the official development line. >>>>>>>>>>>>> >>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>>>>>>> two. >>>>>>>>>>>>> >>>>>>>>>>>>> Regards, >>>>>>>>>>>>> Andreas >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>>> latest >>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>>> Lib...@li... >>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>>> hd...@gm... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>> hd...@gm... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>> latest >>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>> Lib...@li... >>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest >>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>> _______________________________________________ >>>>>>>>>> Libposix-development mailing list >>>>>>>>>> Lib...@li... >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Henrique Dante de Almeida >>>>>>>>> hd...@gm... >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Henrique Dante de Almeida >>>>>>>> hd...@gm... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-13 16:31:38
|
Henrique, I'm not pulling the struct definition out of my a**, Linux is the way it is (especially its kernel data structures), and there's nothing that can be changed about it from my side. If this is unacceptable, well, then I can't help you. Take the code or leave it, it's all your decision. Having to vindicate every single line of code that I contribute isn't exactly something that makes me eager to contribute more code. Best regards, Andreas On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote: > Comments for commit: > > 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system > calls (including auto-generator script). > > signal.h: > - the "include" files can't contain conditional code (_WORDSIZE), > move signal.h to system specific directories (or add an #include > <arch_signal.h>) > stat.h: > - __pad0, __st_ino, etc. where did those come from ? > - can't have __attribute__ extension in "include" directory (where > did those come from ?) > - sigval_t this doesn't exist in the standard > > Are you copying this from an older implementation ? There are too many > unexpected features in this patch. I need to understand what's this > all about before I continue reading the patches. I can't spend time > verifying that non standard code is being submitted, this has to be > done by the contributor. > > 2009/6/12 Henrique Almeida <hd...@gm...>: >> Comments for commit: >> >> 9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build. >> >> - uncomment #ifdef in syscall_nums.h >> - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi >> >> 2009/6/9 Henrique Almeida <hd...@gm...>: >>> Broken branch updated up to 2009-06-05 >>> >>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>> Comments for commit: >>>> >>>> 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() >>>> including unit tests. >>>> >>>> on strrchr.c, '\0' must be considered part of the string, fix both >>>> the implementation and test >>>> >>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>> Comments for commit: >>>>> >>>>> d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already >>>>> implemented str* functions. >>>>> >>>>> - remove test prefix from file names >>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is >>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 >>>>> - add test coverage to strcmp: range 0, UCHAR_MAX >>>>> - add test coverage to strcpy: out of bound writes (both sides) >>>>> >>>>> >>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>> Comments for commit: >>>>>> >>>>>> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >>>>>> >>>>>> - sys/mman.h >>>>>> - the PROT_* macros are system dependent (they depend on the kernel used). >>>>>> mman.h should be moved to the system directory. Also, the reference for >>>>>> the values for linux are missing. >>>>>> >>>>>> >>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>>> >>>>>>> I have done a git pull here and there are individual commits. I think I >>>>>>> haven't noticed them earlier. I'll begin to read each of them. >>>>>>> >>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>>>>>> >>>>>>>> The problem was that the merge was condensed into a single commit (or >>>>>>>> maybe I didn't notice the other commits in the log). I can try again later, >>>>>>>> but at the moment there are some merge issues to resolve. >>>>>>>> >>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>>>>>> >>>>>>>>> If there are differences, you always need an extra merge commit, as far >>>>>>>>> as I understand. >>>>>>>>> >>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>>>>>> my branch: >>>>>>>>>> >>>>>>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>>>>>> Merge: 1faac1a... 05b56ea... >>>>>>>>>> Author: Henrique <hd...@us...> >>>>>>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>>>>>> >>>>>>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>>>>>> >>>>>>>>>> * git://github.com/akrennmair/libposix: >>>>>>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>>>>>> implemented strrchr() including unit tests. >>>>>>>>>> fixed build dependencies for tests. >>>>>>>>>> added unit tests for already implemented str* functions. >>>>>>>>>> added mmap and munmap. >>>>>>>>>> added simple unit tests for already implemented mem* functions. >>>>>>>>>> >>>>>>>>>> Is there a way to fix this ? >>>>>>>>>> >>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>>>>>> >>>>>>>>>>> Ok, good idea, git branches rock ! >>>>>>>>>>> >>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>>>>>> >>>>>>>>>>>> Hello everybody, >>>>>>>>>>>> >>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>>>>>> official libposix repository by executing >>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>>>>>> easier to reintegrate with the official development line. >>>>>>>>>>>> >>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>>>>>> two. >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> Andreas >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>>> latest >>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>>> Lib...@li... >>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>>> hd...@gm... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>> hd...@gm... >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>> latest >>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>> _______________________________________________ >>>>>>>>>> Libposix-development mailing list >>>>>>>>>> Lib...@li... >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>> looking to deploy the next generation of Solaris that includes the latest >>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>> _______________________________________________ >>>>>>>>> Libposix-development mailing list >>>>>>>>> Lib...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Henrique Dante de Almeida >>>>>>>> hd...@gm... >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > |
|
From: Henrique A. <hd...@gm...> - 2009-06-13 03:21:52
|
Comments for commit: 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system calls (including auto-generator script). signal.h: - the "include" files can't contain conditional code (_WORDSIZE), move signal.h to system specific directories (or add an #include <arch_signal.h>) stat.h: - __pad0, __st_ino, etc. where did those come from ? - can't have __attribute__ extension in "include" directory (where did those come from ?) - sigval_t this doesn't exist in the standard Are you copying this from an older implementation ? There are too many unexpected features in this patch. I need to understand what's this all about before I continue reading the patches. I can't spend time verifying that non standard code is being submitted, this has to be done by the contributor. 2009/6/12 Henrique Almeida <hd...@gm...>: > Comments for commit: > > 9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build. > > - uncomment #ifdef in syscall_nums.h > - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi > > 2009/6/9 Henrique Almeida <hd...@gm...>: >> Broken branch updated up to 2009-06-05 >> >> 2009/6/9 Henrique Almeida <hd...@gm...>: >>> Comments for commit: >>> >>> 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() >>> including unit tests. >>> >>> on strrchr.c, '\0' must be considered part of the string, fix both >>> the implementation and test >>> >>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>> Comments for commit: >>>> >>>> d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already >>>> implemented str* functions. >>>> >>>> - remove test prefix from file names >>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is >>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 >>>> - add test coverage to strcmp: range 0, UCHAR_MAX >>>> - add test coverage to strcpy: out of bound writes (both sides) >>>> >>>> >>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>> Comments for commit: >>>>> >>>>> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >>>>> >>>>> - sys/mman.h >>>>> - the PROT_* macros are system dependent (they depend on the kernel used). >>>>> mman.h should be moved to the system directory. Also, the reference for >>>>> the values for linux are missing. >>>>> >>>>> >>>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>>> >>>>>> I have done a git pull here and there are individual commits. I think I >>>>>> haven't noticed them earlier. I'll begin to read each of them. >>>>>> >>>>>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>>>>> >>>>>>> The problem was that the merge was condensed into a single commit (or >>>>>>> maybe I didn't notice the other commits in the log). I can try again later, >>>>>>> but at the moment there are some merge issues to resolve. >>>>>>> >>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>>>>> >>>>>>>> If there are differences, you always need an extra merge commit, as far >>>>>>>> as I understand. >>>>>>>> >>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>>>>> my branch: >>>>>>>>> >>>>>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>>>>> Merge: 1faac1a... 05b56ea... >>>>>>>>> Author: Henrique <hd...@us...> >>>>>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>>>>> >>>>>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>>>>> >>>>>>>>> * git://github.com/akrennmair/libposix: >>>>>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>>>>> implemented strrchr() including unit tests. >>>>>>>>> fixed build dependencies for tests. >>>>>>>>> added unit tests for already implemented str* functions. >>>>>>>>> added mmap and munmap. >>>>>>>>> added simple unit tests for already implemented mem* functions. >>>>>>>>> >>>>>>>>> Is there a way to fix this ? >>>>>>>>> >>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>>>>> >>>>>>>>>> Ok, good idea, git branches rock ! >>>>>>>>>> >>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>>>>> >>>>>>>>>>> Hello everybody, >>>>>>>>>>> >>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>>>>> official libposix repository by executing >>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>>>>> easier to reintegrate with the official development line. >>>>>>>>>>> >>>>>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>>>>> two. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> Andreas >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>>> latest >>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Libposix-development mailing list >>>>>>>>>>> Lib...@li... >>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Henrique Dante de Almeida >>>>>>>>>> hd...@gm... >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Henrique Dante de Almeida >>>>>>>>> hd...@gm... >>>>>>>>> >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>> latest >>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>> _______________________________________________ >>>>>>>>> Libposix-development mailing list >>>>>>>>> Lib...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>> looking to deploy the next generation of Solaris that includes the latest >>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>> _______________________________________________ >>>>>>>> Libposix-development mailing list >>>>>>>> Lib...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-13 02:45:19
|
Comments for commit: 9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build. - uncomment #ifdef in syscall_nums.h - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi 2009/6/9 Henrique Almeida <hd...@gm...>: > Broken branch updated up to 2009-06-05 > > 2009/6/9 Henrique Almeida <hd...@gm...>: >> Comments for commit: >> >> 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() >> including unit tests. >> >> on strrchr.c, '\0' must be considered part of the string, fix both >> the implementation and test >> >> 2009/6/9 Henrique Almeida <hd...@gm...>: >>> Comments for commit: >>> >>> d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already >>> implemented str* functions. >>> >>> - remove test prefix from file names >>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is >>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 >>> - add test coverage to strcmp: range 0, UCHAR_MAX >>> - add test coverage to strcpy: out of bound writes (both sides) >>> >>> >>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>> Comments for commit: >>>> >>>> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >>>> >>>> - sys/mman.h >>>> - the PROT_* macros are system dependent (they depend on the kernel used). >>>> mman.h should be moved to the system directory. Also, the reference for >>>> the values for linux are missing. >>>> >>>> >>>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>>> >>>>> I have done a git pull here and there are individual commits. I think I >>>>> haven't noticed them earlier. I'll begin to read each of them. >>>>> >>>>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>>>> >>>>>> The problem was that the merge was condensed into a single commit (or >>>>>> maybe I didn't notice the other commits in the log). I can try again later, >>>>>> but at the moment there are some merge issues to resolve. >>>>>> >>>>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>>>> >>>>>>> If there are differences, you always need an extra merge commit, as far >>>>>>> as I understand. >>>>>>> >>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>>>> wrote: >>>>>>>> >>>>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>>>> my branch: >>>>>>>> >>>>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>>>> Merge: 1faac1a... 05b56ea... >>>>>>>> Author: Henrique <hd...@us...> >>>>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>>>> >>>>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>>>> >>>>>>>> * git://github.com/akrennmair/libposix: >>>>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>>>> implemented strrchr() including unit tests. >>>>>>>> fixed build dependencies for tests. >>>>>>>> added unit tests for already implemented str* functions. >>>>>>>> added mmap and munmap. >>>>>>>> added simple unit tests for already implemented mem* functions. >>>>>>>> >>>>>>>> Is there a way to fix this ? >>>>>>>> >>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>>>> >>>>>>>>> Ok, good idea, git branches rock ! >>>>>>>>> >>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>>>> >>>>>>>>>> Hello everybody, >>>>>>>>>> >>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>>>> official libposix repository by executing >>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>>>> easier to reintegrate with the official development line. >>>>>>>>>> >>>>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>>>> two. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Andreas >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>>> latest >>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>>> _______________________________________________ >>>>>>>>>> Libposix-development mailing list >>>>>>>>>> Lib...@li... >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Henrique Dante de Almeida >>>>>>>>> hd...@gm... >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Henrique Dante de Almeida >>>>>>>> hd...@gm... >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>> latest >>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>> _______________________________________________ >>>>>>>> Libposix-development mailing list >>>>>>>> Lib...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>> looking to deploy the next generation of Solaris that includes the latest >>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>> _______________________________________________ >>>>>>> Libposix-development mailing list >>>>>>> Lib...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-12 14:47:49
|
Wow, a lot of work has been done. :-D Congratulations, both ! 2009/6/12 Andreas Krennmair <akr...@go...>: > Hello everyone, > > Here's an overview over my most recent development wrt. libposix. All > changes can be found in my development branch here: > http://github.com/akrennmair/libposix/tree/master > > First of all, I added a list of system calls, most of which are still > completely untested. The majority of them is automatically generated > as they're nothing but thin wrappers around the syscall* functions. > Many of the used structures are still incomplete. > > I also added an install target to the Makefile and a wrapper script > (written in Perl) that makes it easy to compile and link C files > against libposix. Instead of calling > $ gcc -c foo.c -o foo.o > and > $ gcc -o foo foo.o bar.o quux.o > You can simply write > $ psx08 gcc -c foo.c -o foo.o > and > $ psx08 gcc -o foo foo.o bar.o quux.o > and the psx08 wrapper will adjust the gcc commandline to correctly > compile and/or link against libposix. In theory, using a configure > script to compile/link a program with libposix, all that you need is > $ CC="psx08 gcc" ./configure ... > In practice, most of the functionality to compile and link most > non-trivial programs is still missing, though. This wrapper is also > used to compile and link all available tests. > > Another thing that I implemented was an implementation of malloc(), > free(), realloc() and calloc(). Only very basic tests have currently > been implemented, and more effort is still necessary. The > implementation is prepared to use both brk() and mmap() to allocate > memory, but due to an issue with mmap() (it returns a pointer which, > when dereferenced, immediately leads to a SIGSEGV), some parts are > currently commented out to disable the use of mmap(). It's really only > a simple implementation, as it uses mmap() for allocation of 8 kb or > bigger, and brk() and a simple first-fit algorithm to allocate smaller > chunks. > > Support for errno is now available, too! Some testing still required, though. > > Nico Golde contributed implementations of memccpy and atoi including > unit tests in yesterday's libposix hacking session of him and me. He > also added a list of all system interfaces in POSIX.1-2008 where all > currently implemented system interfaces are marked to easily see which > functions are already done and which are still to be implemented. > > And last but not least, I added simple ASCII-based implementations of > the is* functions of ctype.h including unit tests. This must be > improved as soon as there's a proper locale implementation available. > > Please bear in mind that all my changes are Linux- and x86_64-specific. > > Regards, > Andreas > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-12 08:50:34
|
Hello everyone, Here's an overview over my most recent development wrt. libposix. All changes can be found in my development branch here: http://github.com/akrennmair/libposix/tree/master First of all, I added a list of system calls, most of which are still completely untested. The majority of them is automatically generated as they're nothing but thin wrappers around the syscall* functions. Many of the used structures are still incomplete. I also added an install target to the Makefile and a wrapper script (written in Perl) that makes it easy to compile and link C files against libposix. Instead of calling $ gcc -c foo.c -o foo.o and $ gcc -o foo foo.o bar.o quux.o You can simply write $ psx08 gcc -c foo.c -o foo.o and $ psx08 gcc -o foo foo.o bar.o quux.o and the psx08 wrapper will adjust the gcc commandline to correctly compile and/or link against libposix. In theory, using a configure script to compile/link a program with libposix, all that you need is $ CC="psx08 gcc" ./configure ... In practice, most of the functionality to compile and link most non-trivial programs is still missing, though. This wrapper is also used to compile and link all available tests. Another thing that I implemented was an implementation of malloc(), free(), realloc() and calloc(). Only very basic tests have currently been implemented, and more effort is still necessary. The implementation is prepared to use both brk() and mmap() to allocate memory, but due to an issue with mmap() (it returns a pointer which, when dereferenced, immediately leads to a SIGSEGV), some parts are currently commented out to disable the use of mmap(). It's really only a simple implementation, as it uses mmap() for allocation of 8 kb or bigger, and brk() and a simple first-fit algorithm to allocate smaller chunks. Support for errno is now available, too! Some testing still required, though. Nico Golde contributed implementations of memccpy and atoi including unit tests in yesterday's libposix hacking session of him and me. He also added a list of all system interfaces in POSIX.1-2008 where all currently implemented system interfaces are marked to easily see which functions are already done and which are still to be implemented. And last but not least, I added simple ASCII-based implementations of the is* functions of ctype.h including unit tests. This must be improved as soon as there's a proper locale implementation available. Please bear in mind that all my changes are Linux- and x86_64-specific. Regards, Andreas |
|
From: Henrique A. <hd...@gm...> - 2009-06-10 02:37:30
|
Broken branch updated up to 2009-06-05 2009/6/9 Henrique Almeida <hd...@gm...>: > Comments for commit: > > 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() > including unit tests. > > on strrchr.c, '\0' must be considered part of the string, fix both > the implementation and test > > 2009/6/9 Henrique Almeida <hd...@gm...>: >> Comments for commit: >> >> d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already >> implemented str* functions. >> >> - remove test prefix from file names >> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is >> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 >> - add test coverage to strcmp: range 0, UCHAR_MAX >> - add test coverage to strcpy: out of bound writes (both sides) >> >> >> 2009/6/9 Henrique Almeida <hd...@gm...>: >>> Comments for commit: >>> >>> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >>> >>> - sys/mman.h >>> - the PROT_* macros are system dependent (they depend on the kernel used). >>> mman.h should be moved to the system directory. Also, the reference for >>> the values for linux are missing. >>> >>> >>> 2009/6/9 Henrique Almeida <hd...@gm...>: >>>> >>>> I have done a git pull here and there are individual commits. I think I >>>> haven't noticed them earlier. I'll begin to read each of them. >>>> >>>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>>> >>>>> The problem was that the merge was condensed into a single commit (or >>>>> maybe I didn't notice the other commits in the log). I can try again later, >>>>> but at the moment there are some merge issues to resolve. >>>>> >>>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>>> >>>>>> If there are differences, you always need an extra merge commit, as far >>>>>> as I understand. >>>>>> >>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>>> wrote: >>>>>>> >>>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>>> my branch: >>>>>>> >>>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>>> Merge: 1faac1a... 05b56ea... >>>>>>> Author: Henrique <hd...@us...> >>>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>>> >>>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>>> >>>>>>> * git://github.com/akrennmair/libposix: >>>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>>> implemented strrchr() including unit tests. >>>>>>> fixed build dependencies for tests. >>>>>>> added unit tests for already implemented str* functions. >>>>>>> added mmap and munmap. >>>>>>> added simple unit tests for already implemented mem* functions. >>>>>>> >>>>>>> Is there a way to fix this ? >>>>>>> >>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>>> >>>>>>>> Ok, good idea, git branches rock ! >>>>>>>> >>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>>> >>>>>>>>> Hello everybody, >>>>>>>>> >>>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>>> official libposix repository by executing >>>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>>> easier to reintegrate with the official development line. >>>>>>>>> >>>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>>> two. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Andreas >>>>>>>>> >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>>> latest >>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>>> _______________________________________________ >>>>>>>>> Libposix-development mailing list >>>>>>>>> Lib...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Henrique Dante de Almeida >>>>>>>> hd...@gm... >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>> latest >>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>> _______________________________________________ >>>>>>> Libposix-development mailing list >>>>>>> Lib...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>> looking to deploy the next generation of Solaris that includes the latest >>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>> _______________________________________________ >>>>>> Libposix-development mailing list >>>>>> Lib...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-10 02:33:23
|
Comments for commit: 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr() including unit tests. on strrchr.c, '\0' must be considered part of the string, fix both the implementation and test 2009/6/9 Henrique Almeida <hd...@gm...>: > Comments for commit: > > d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already > implemented str* functions. > > - remove test prefix from file names > - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is > incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 > - add test coverage to strcmp: range 0, UCHAR_MAX > - add test coverage to strcpy: out of bound writes (both sides) > > > 2009/6/9 Henrique Almeida <hd...@gm...>: >> Comments for commit: >> >> 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. >> >> - sys/mman.h >> - the PROT_* macros are system dependent (they depend on the kernel used). >> mman.h should be moved to the system directory. Also, the reference for >> the values for linux are missing. >> >> >> 2009/6/9 Henrique Almeida <hd...@gm...>: >>> >>> I have done a git pull here and there are individual commits. I think I >>> haven't noticed them earlier. I'll begin to read each of them. >>> >>> 2009/6/8 Henrique Almeida <hd...@gm...> >>>> >>>> The problem was that the merge was condensed into a single commit (or >>>> maybe I didn't notice the other commits in the log). I can try again later, >>>> but at the moment there are some merge issues to resolve. >>>> >>>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>>> >>>>> If there are differences, you always need an extra merge commit, as far >>>>> as I understand. >>>>> >>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>>> wrote: >>>>>> >>>>>> With git pull, I'm not being able to merge each commit individually in >>>>>> my branch: >>>>>> >>>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>>> Merge: 1faac1a... 05b56ea... >>>>>> Author: Henrique <hd...@us...> >>>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>>> >>>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>>> >>>>>> * git://github.com/akrennmair/libposix: >>>>>> implemented abs(), labs() and llabs() including unit tests. >>>>>> implemented strrchr() including unit tests. >>>>>> fixed build dependencies for tests. >>>>>> added unit tests for already implemented str* functions. >>>>>> added mmap and munmap. >>>>>> added simple unit tests for already implemented mem* functions. >>>>>> >>>>>> Is there a way to fix this ? >>>>>> >>>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>>> >>>>>>> Ok, good idea, git branches rock ! >>>>>>> >>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>>> >>>>>>>> Hello everybody, >>>>>>>> >>>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>>> official libposix repository by executing >>>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>>> easier to reintegrate with the official development line. >>>>>>>> >>>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>>> two. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Andreas >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>>> latest >>>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>>> _______________________________________________ >>>>>>>> Libposix-development mailing list >>>>>>>> Lib...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Henrique Dante de Almeida >>>>>>> hd...@gm... >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>> looking to deploy the next generation of Solaris that includes the >>>>>> latest >>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>> _______________________________________________ >>>>>> Libposix-development mailing list >>>>>> Lib...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>> looking to deploy the next generation of Solaris that includes the latest >>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-10 02:31:33
|
Comments for commit:
609bece7a56497fa49fb6f07d38beaaa31368f60 added simple unit tests for
already implemented mem* functions.
- move test output to the output directory
- remove test prefix from file names
- add more test coverage on memchr:
- 0~UCHAR_MAX range, border values
- "borderline standard": memchr(x, -1, s) | x = { 0, 0, UCHAR_MAX, 0, 0 },
memchr(x, 5*UCHAR_MAX+47, s), etc.
- more coverage to memcmp: less or greater than, 0~UCHAR_MAX range
- more coverage to memcpy: return value, out of bounds copy (both sides), range
- more coverage to memmove: return value, oob both sides, range
- merge memmove tests into a single file
- more coverage to memset: return value, arbitrary integer values related
to UCHAR_MAX modular arithmetic, oob both sides
2009/6/4 Andreas Krennmair <akr...@go...>
>
> Hello everyone,
>
> I started with a simple set of unit tests to have some test coverage and an integration into the build system to automatically run tests. So far, only the already implemented mem* routines are covered: http://synflood.at/tmp/libposix/unit-tests-mem.mbox
>
> Regards,
> Andreas
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>
--
Henrique Dante de Almeida
hd...@gm...
|
|
From: Henrique A. <hd...@gm...> - 2009-06-10 02:23:47
|
Comments for commit: d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already implemented str* functions. - remove test prefix from file names - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13 - add test coverage to strcmp: range 0, UCHAR_MAX - add test coverage to strcpy: out of bound writes (both sides) 2009/6/9 Henrique Almeida <hd...@gm...>: > Comments for commit: > > 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. > > - sys/mman.h > - the PROT_* macros are system dependent (they depend on the kernel used). > mman.h should be moved to the system directory. Also, the reference for > the values for linux are missing. > > > 2009/6/9 Henrique Almeida <hd...@gm...>: >> >> I have done a git pull here and there are individual commits. I think I >> haven't noticed them earlier. I'll begin to read each of them. >> >> 2009/6/8 Henrique Almeida <hd...@gm...> >>> >>> The problem was that the merge was condensed into a single commit (or >>> maybe I didn't notice the other commits in the log). I can try again later, >>> but at the moment there are some merge issues to resolve. >>> >>> 2009/6/8 Andreas Krennmair <akr...@go...> >>>> >>>> If there are differences, you always need an extra merge commit, as far >>>> as I understand. >>>> >>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>>> wrote: >>>>> >>>>> With git pull, I'm not being able to merge each commit individually in >>>>> my branch: >>>>> >>>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>>> Merge: 1faac1a... 05b56ea... >>>>> Author: Henrique <hd...@us...> >>>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>>> >>>>> Merge git://github.com/akrennmair/libposix into andreas >>>>> >>>>> * git://github.com/akrennmair/libposix: >>>>> implemented abs(), labs() and llabs() including unit tests. >>>>> implemented strrchr() including unit tests. >>>>> fixed build dependencies for tests. >>>>> added unit tests for already implemented str* functions. >>>>> added mmap and munmap. >>>>> added simple unit tests for already implemented mem* functions. >>>>> >>>>> Is there a way to fix this ? >>>>> >>>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>>> >>>>>> Ok, good idea, git branches rock ! >>>>>> >>>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>>> >>>>>>> Hello everybody, >>>>>>> >>>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>>> In this fork, I will regularly keep track of changes in the official >>>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>>> official libposix repository by executing >>>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>>> interpreted as a way to get independent from the official project, it is >>>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>>> easier to reintegrate with the official development line. >>>>>>> >>>>>>> Nevertheless, I will continue posting short notifications about the >>>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>>> two. >>>>>>> >>>>>>> Regards, >>>>>>> Andreas >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>>> looking to deploy the next generation of Solaris that includes the >>>>>>> latest >>>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>>> _______________________________________________ >>>>>>> Libposix-development mailing list >>>>>>> Lib...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Henrique Dante de Almeida >>>>>> hd...@gm... >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>> looking to deploy the next generation of Solaris that includes the >>>>> latest >>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>> looking to deploy the next generation of Solaris that includes the latest >>>> innovations from Sun and the OpenSource community. Download a copy and >>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-10 02:08:48
|
Comments for commit: 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap. - sys/mman.h - the PROT_* macros are system dependent (they depend on the kernel used). mman.h should be moved to the system directory. Also, the reference for the values for linux are missing. 2009/6/9 Henrique Almeida <hd...@gm...>: > > I have done a git pull here and there are individual commits. I think I > haven't noticed them earlier. I'll begin to read each of them. > > 2009/6/8 Henrique Almeida <hd...@gm...> >> >> The problem was that the merge was condensed into a single commit (or >> maybe I didn't notice the other commits in the log). I can try again later, >> but at the moment there are some merge issues to resolve. >> >> 2009/6/8 Andreas Krennmair <akr...@go...> >>> >>> If there are differences, you always need an extra merge commit, as far >>> as I understand. >>> >>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> >>> wrote: >>>> >>>> With git pull, I'm not being able to merge each commit individually in >>>> my branch: >>>> >>>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>>> Merge: 1faac1a... 05b56ea... >>>> Author: Henrique <hd...@us...> >>>> Date: Sat Jun 6 17:29:37 2009 -0300 >>>> >>>> Merge git://github.com/akrennmair/libposix into andreas >>>> >>>> * git://github.com/akrennmair/libposix: >>>> implemented abs(), labs() and llabs() including unit tests. >>>> implemented strrchr() including unit tests. >>>> fixed build dependencies for tests. >>>> added unit tests for already implemented str* functions. >>>> added mmap and munmap. >>>> added simple unit tests for already implemented mem* functions. >>>> >>>> Is there a way to fix this ? >>>> >>>> 2009/6/5 Henrique Almeida <hd...@gm...> >>>>> >>>>> Ok, good idea, git branches rock ! >>>>> >>>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>>>> >>>>>> Hello everybody, >>>>>> >>>>>> As the "broken" branch didn't work out as expected, I found a better >>>>>> way that both satisfies me in its abilities and also allows other developers >>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>>> In this fork, I will regularly keep track of changes in the official >>>>>> libposix git repository. But it's also simple to merge my commits into the >>>>>> official libposix repository by executing >>>>>> git pull git://github.com/akrennmair/libposix.git master >>>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>>> the place to see and track my changes. Of course, this shall NOT be >>>>>> interpreted as a way to get independent from the official project, it is >>>>>> merely a way that helps me work in a more flexible fashion on the things >>>>>> that I want to work on, plus it makes my changes more visible and also >>>>>> easier to reintegrate with the official development line. >>>>>> >>>>>> Nevertheless, I will continue posting short notifications about the >>>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>>> some simple functions including unit tests, and I hope to present a simple >>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>>> two. >>>>>> >>>>>> Regards, >>>>>> Andreas >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>>> looking to deploy the next generation of Solaris that includes the >>>>>> latest >>>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>>> _______________________________________________ >>>>>> Libposix-development mailing list >>>>>> Lib...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Henrique Dante de Almeida >>>>> hd...@gm... >>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>> looking to deploy the next generation of Solaris that includes the >>>> latest >>>> innovations from Sun and the OpenSource community. Download a copy and >>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>> _______________________________________________ >>>> Libposix-development mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>> looking to deploy the next generation of Solaris that includes the latest >>> innovations from Sun and the OpenSource community. Download a copy and >>> enjoy capabilities such as Networking, Storage and Virtualization. >>> Go to: http://p.sf.net/sfu/opensolaris-get >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-10 01:00:26
|
I have done a git pull here and there are individual commits. I think I haven't noticed them earlier. I'll begin to read each of them. 2009/6/8 Henrique Almeida <hd...@gm...> > > The problem was that the merge was condensed into a single commit (or > maybe I didn't notice the other commits in the log). I can try again later, > but at the moment there are some merge issues to resolve. > > 2009/6/8 Andreas Krennmair <akr...@go...> > > If there are differences, you always need an extra merge commit, as far as >> I understand. >> >> >> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote: >> >>> >>> With git pull, I'm not being able to merge each commit individually in >>> my branch: >>> >>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>> Merge: 1faac1a... 05b56ea... >>> Author: Henrique <hd...@us...> >>> Date: Sat Jun 6 17:29:37 2009 -0300 >>> >>> Merge git://github.com/akrennmair/libposix into andreas >>> >>> * git://github.com/akrennmair/libposix: >>> implemented abs(), labs() and llabs() including unit tests. >>> implemented strrchr() including unit tests. >>> fixed build dependencies for tests. >>> added unit tests for already implemented str* functions. >>> added mmap and munmap. >>> added simple unit tests for already implemented mem* functions. >>> >>> Is there a way to fix this ? >>> >>> 2009/6/5 Henrique Almeida <hd...@gm...> >>> >>> >>>> Ok, good idea, git branches rock ! >>>> >>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>> >>>>> Hello everybody, >>>>> >>>>> As the "broken" branch didn't work out as expected, I found a better >>>>> way that both satisfies me in its abilities and also allows other developers >>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>> In this fork, I will regularly keep track of changes in the official >>>>> libposix git repository. But it's also simple to merge my commits into the >>>>> official libposix repository by executing >>>>> git pull git://github.com/akrennmair/libposix.git master >>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>> the place to see and track my changes. Of course, this shall NOT be >>>>> interpreted as a way to get independent from the official project, it is >>>>> merely a way that helps me work in a more flexible fashion on the things >>>>> that I want to work on, plus it makes my changes more visible and also >>>>> easier to reintegrate with the official development line. >>>>> >>>>> Nevertheless, I will continue posting short notifications about the >>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>> some simple functions including unit tests, and I hope to present a simple >>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>> two. >>>>> >>>>> Regards, >>>>> Andreas >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>> looking to deploy the next generation of Solaris that includes the >>>>> latest >>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >>> >>> ------------------------------------------------------------------------------ >>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>> looking to deploy the next generation of Solaris that includes the latest >>> innovations from Sun and the OpenSource community. Download a copy and >>> enjoy capabilities such as Networking, Storage and Virtualization. >>> Go to: http://p.sf.net/sfu/opensolaris-get >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >>> >> >> >> ------------------------------------------------------------------------------ >> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >> looking to deploy the next generation of Solaris that includes the latest >> innovations from Sun and the OpenSource community. Download a copy and >> enjoy capabilities such as Networking, Storage and Virtualization. >> Go to: http://p.sf.net/sfu/opensolaris-get >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >> > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Henrique A. <hd...@gm...> - 2009-06-10 00:56:56
|
I've just been told that the wiki is not working. I'll try to fix this tomorrow. I've received a message from Sourceforge saying that soon they'll better integrate all the third party apps and separate logins will disappear. 2009/6/3 Henrique Almeida <hd...@gm...> > I've added functions starting with U to the wiki. Let's finish this > task. I'll take the remaining functions after wcsncat. > > Those who have already posted their list, please convert it to the > wiki format and update the wiki. > > 2009/6/2 Henrique Almeida <hd...@gm...>: > > I've created the page. See if it can be edited. > > > > > https://apps.sourceforge.net/mediawiki/libposix/index.php?title=Function_list > > > > 2009/5/31 Henrique Almeida <hd...@gm...>: > >> While they don't answer, I was able to put you in the "editor" group. > >> > >> 2009/5/31 Henrique Almeida <hd...@gm...>: > >>> I want to give full access to the wiki, but I have no idea how to do > >>> that. I'll send a message to SF. > >>> > >>> 2009/5/31 David Rocamora <dr...@gm...>: > >>>> Henrique, > >>>> > >>>> Can you open up the permissions on the wiki so I can create a page > >>>> called "function list" or what not. I think we should start with the > >>>> list we are describing there and have each function link to another > >>>> wiki page if more description is needed. The wiki seems locked down > >>>> now so I can't add the page myself. > >>>> > >>>> Thanks, > >>>> Dave > >>>> > >>>> On Thu, May 28, 2009 at 3:23 PM, Henrique Almeida <hd...@gm...> > wrote: > >>>>> > >>>>> > >>>>> 2009/5/28 Tordek <ke...@gm...>: > >>>>>> Henrique Almeida wrote: > >>>>>>> First of all, I hope the message reaches everyone, I'm not sure if > >>>>>>> the mailing list is working well, so please reply to this post if > >>>>>>> you've received it. > >>>>>>> > >>>>>> > >>>>>> Yes, it is. > >>>>> > >>>>> Nice. > >>>>> > >>>>>>> We'll start the project with a simple task. During the project > we'll > >>>>>>> need to mantain the list with the status of each function in the > >>>>>>> project (that is, if it has been implemented, tested, etc.). > >>>>>> > >>>>>> Do we have a wiki, or another place to post this to? A specific > >>>>>> format? (writing the full description of a function as an example > >>>>>> would be a great start). > >>>>>> > >>>>>> I'd strongly reccomend a wiki, to make it highly navigable > >>>>>> (categorizing functions per difficulty, and implementedness, for > one). > >>>>> > >>>>> Yes, we definitely need a wiki. SF provides MediaWiki. I have > activated it > >>>>> on: > >>>>> > >>>>> > http://apps.sourceforge.net/mediawiki/libposix/index.php?title=Main_Page > >>>>> > >>>>> However, at some moment we'll need to provide a clean and uniform > (and > >>>>> unique) appearance to the whole site, so we'll need to play with the > CSS > >>>>> stuff in the wiki. Can you do this ? (btw, we'll need to setup a task > >>>>> management page too) > >>>>> > >>>>> At the moment, the table needs the following > >>>>> - function name > >>>>> - requirement (mandatory or the option group which it belongs) > >>>>> - whether it's obsolescent or not > >>>>> - expected difficulty > >>>>> > >>>>> The table will grow later, but let's keep it simple for now. For the > >>>>> functions atoi, crypt and dprintf that would be: > >>>>> > >>>>> atoi mandatory (not obsolescent) easy > >>>>> crypt XSI option (not obsolescent) medium > >>>>> dprintf mandatory (not obsolescent) hard > >>>>> > >>>>> There's another wiki available in SF, called Wikispaces, I don't > know if it > >>>>> would be better than MediaWiki, though, I've looked at their home > page and > >>>>> it doesn't seem to be any docs there. > >>>>> > >>>>>> > >>>>>> -- > >>>>>> Guillermo O. «Tordek» Freschi. Programador, Escritor, Genio Maligno. > >>>>>> http://tordek.com.ar :: http://twitter.com/tordek > >>>>>> http://www.arcanopedia.com.ar - Juegos de Rol en Argentina > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Henrique Dante de Almeida > >>>>> hd...@gm... > >>>>> > >>>>> > >>>>> > ------------------------------------------------------------------------------ > >>>>> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > >>>>> is a gathering of tech-side developers & brand creativity > professionals. > >>>>> Meet > >>>>> the minds behind Google Creative Lab, Visual Complexity, Processing, > & > >>>>> iPhoneDevCamp as they present alongside digital heavyweights like > Barbarian > >>>>> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > >>>>> _______________________________________________ > >>>>> Libposix-development mailing list > >>>>> Lib...@li... > >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development > >>>>> > >>>>> > >>>> > >>> > >>> > >>> > >>> -- > >>> Henrique Dante de Almeida > >>> hd...@gm... > >>> > >> > >> > >> > >> -- > >> Henrique Dante de Almeida > >> hd...@gm... > >> > > > > > > > > -- > > Henrique Dante de Almeida > > hd...@gm... > > > > > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
|
From: Andreas K. <akr...@go...> - 2009-06-08 16:00:43
|
No, all commits are included and kept separata (that's how it's supposed to be, after all), sometimes you just need an additional merge commit that fixes all the merge issues. It's as simple as that. Regards, Andreas On Mon, Jun 8, 2009 at 5:24 PM, Henrique Almeida <hd...@gm...> wrote: > > The problem was that the merge was condensed into a single commit (or > maybe I didn't notice the other commits in the log). I can try again later, > but at the moment there are some merge issues to resolve. > > 2009/6/8 Andreas Krennmair <akr...@go...> > > If there are differences, you always need an extra merge commit, as far as >> I understand. >> >> >> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote: >> >>> >>> With git pull, I'm not being able to merge each commit individually in >>> my branch: >>> >>> commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd >>> Merge: 1faac1a... 05b56ea... >>> Author: Henrique <hd...@us...> >>> Date: Sat Jun 6 17:29:37 2009 -0300 >>> >>> Merge git://github.com/akrennmair/libposix into andreas >>> >>> * git://github.com/akrennmair/libposix: >>> implemented abs(), labs() and llabs() including unit tests. >>> implemented strrchr() including unit tests. >>> fixed build dependencies for tests. >>> added unit tests for already implemented str* functions. >>> added mmap and munmap. >>> added simple unit tests for already implemented mem* functions. >>> >>> Is there a way to fix this ? >>> >>> 2009/6/5 Henrique Almeida <hd...@gm...> >>> >>> >>>> Ok, good idea, git branches rock ! >>>> >>>> 2009/6/5 Andreas Krennmair <akr...@go...> >>>> >>>>> Hello everybody, >>>>> >>>>> As the "broken" branch didn't work out as expected, I found a better >>>>> way that both satisfies me in its abilities and also allows other developers >>>>> to easily see and merge my changes. I have a fork of libposix uploaded on >>>>> GitHub: http://github.com/akrennmair/libposix/tree/master >>>>> In this fork, I will regularly keep track of changes in the official >>>>> libposix git repository. But it's also simple to merge my commits into the >>>>> official libposix repository by executing >>>>> git pull git://github.com/akrennmair/libposix.git master >>>>> in a clone of the official libposix git repository. Anyway, GitHub is >>>>> the place to see and track my changes. Of course, this shall NOT be >>>>> interpreted as a way to get independent from the official project, it is >>>>> merely a way that helps me work in a more flexible fashion on the things >>>>> that I want to work on, plus it makes my changes more visible and also >>>>> easier to reintegrate with the official development line. >>>>> >>>>> Nevertheless, I will continue posting short notifications about the >>>>> things I currently work on to keep everyone informed. So far, I've worked on >>>>> some simple functions including unit tests, and I hope to present a simple >>>>> implementation of malloc(), free(), realloc() and calloc() within a day or >>>>> two. >>>>> >>>>> Regards, >>>>> Andreas >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>>>> looking to deploy the next generation of Solaris that includes the >>>>> latest >>>>> innovations from Sun and the OpenSource community. Download a copy and >>>>> enjoy capabilities such as Networking, Storage and Virtualization. >>>>> Go to: http://p.sf.net/sfu/opensolaris-get >>>>> _______________________________________________ >>>>> Libposix-development mailing list >>>>> Lib...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>>>> >>>>> >>>> >>>> >>>> -- >>>> Henrique Dante de Almeida >>>> hd...@gm... >>>> >>> >>> >>> >>> -- >>> Henrique Dante de Almeida >>> hd...@gm... >>> >>> >>> ------------------------------------------------------------------------------ >>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >>> looking to deploy the next generation of Solaris that includes the latest >>> innovations from Sun and the OpenSource community. Download a copy and >>> enjoy capabilities such as Networking, Storage and Virtualization. >>> Go to: http://p.sf.net/sfu/opensolaris-get >>> _______________________________________________ >>> Libposix-development mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libposix-development >>> >>> >> >> >> ------------------------------------------------------------------------------ >> OpenSolaris 2009.06 is a cutting edge operating system for enterprises >> looking to deploy the next generation of Solaris that includes the latest >> innovations from Sun and the OpenSource community. Download a copy and >> enjoy capabilities such as Networking, Storage and Virtualization. >> Go to: http://p.sf.net/sfu/opensolaris-get >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >> > > > -- > Henrique Dante de Almeida > hd...@gm... > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > |
