pikpik / minix-pkgsrc Goto Github PK

Hi,

I created the "xv-port" branch based on Ivan's work to port XV. It appears to compile and run in MINIX 3.1.9, but not in 3.1.8. The reason is that in 3.1.8, <memory.h> refers to a less used file, while in 3.1.9 <memory.h> simply includes <string.h>.

Possible solution:

We could find the code that is having the problem and do the following:

Replace:

#include 

With:

#ifdef __minix
# include 
#else
# include 
#endif

...but I'm not sure if that is a good idea.

Thank you,
pikpik

It's the first time I use git and I'm not very good at it, however I was able to build and install python31, it works like python24 (aka no shared libs, but at least it's there).

Let me know if you have problems, I wanted to add a file with git with explanation of the changes but git isn't working right for me at the moment (I tried "git add myfile" and then "commit" but it said there were no changes...).

Enjoy.

Hey guys... I've ported dbus, it's in the dbus-branch...

I honestly don't know how well this would work and how much it will be needed, being minix3 a micro-kernel and everything, but I was trying to build emacs and dbus was needed for that so... why not? :)

Before you try to install it, though, you need to create a group called dbus and a user called dbus in the dbus group.

After that, it builds beautifully (at least to me).

All I had to do was patch two .c files (patches in the files folder of the package) with a !defined(_MINIX) flag because the OS wasn't recognizing two macros... I know this may be a quick and dirty hack, but it appears to be working now. If anyone has better ideas let me know :)

looking to run a computer without a hard drive but the instructions are not simple enough for me. I also want to build my own windows unattended installer but don't know where to start. if I could get someone to train me that has a time when I get going I could pay you guys back by working on things.

Hi,

I made a new branch called "lcms-and-imagemagick." It has my changes for LCMS and ImageMagick. :)

I'm not sure if the idea is for us to merge our changes or have branches ready for Gautam to merge. Either way, these changes are ready if you want to test them. :D

Thanks!
pikpik

Hi,

I made a new branch called "unzip-port." It has my changes for archivers/unzip.

This is for the effort of converting packages from using MINIX's C library to using the new NetBSD C library.

I'm unsure of some of the changes, because some involved rewriting legacy "MINIX" flags to be "__minix," which is the current flag used to indicate that the platform being compiled on is MINIX. Would this cause problems on legacy systems? Is that fine, as they shouldn't use these changes anyway? For the current source of MINIX, this change appears to have no negative effects.

Another change of relative uncertainty is the avoidance of sections of code flagged by either "BSD" or "BSD4_4." The reason for this change is that MINIX's new NetBSD C library specifically avoids using the "BSD4_4" flag, but with no indication of why [1]. Although I'm confused about avoiding "BSD4_4" code, as I had assumed enabling such code was part of the purpose of the NetBSD C library on MINIX, this change appears to have no negative effects.

Thanks!
pikpik

1. You can see the avoidance of the "BSD4_4" flag here on lines 9 through 11: http://git.minix3.org/?p=minix.git;a=blob;f=nbsd_include/sys/param.h;h=b750a3ecf215ba5502c3ca3aea51896762e4b654;hb=c63a0cfddcd42e04be6ef8833b3975fbbbbfe802