Re: [coLinux-devel] [PATCH] cobuild.sh-20040405-1.patch

[Thomas F. <tf...@no...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Dan+George,

currently I'm using just the following patches for cobuild.sh:

http://www.noto.de/colinux/gcc-3.3.2.diff
MD5SUM: 3efa14af3b00d511c6cc44dbc5fe9b49
(to build the libstdc++)

http://www.noto.de/colinux/w32api-2.4.patch
MD5SUM: 2cd750ccc1e7a443374cad568b9aeb79
(Dan's patch)

http://www.noto.de/colinux/fltk1.diff
MD5SUM: c6c74b7db501863ee134f54d84c55c67
(Dan's patch with small modifications)

It would be nice if we have this patches in the patch directory.

Thanks and regards,
 Thomas

> On Tue, Apr 06, 2004 at 01:02:55AM -0000, Thomas Fritzsche wrote:
>
>> The simplest way would we if Dan could include the patches in colinux or
>> upload them to the colinux-homepage.
>
> All patches necessary to build coLinux should be in the source tarball
> patch/
> directory. I have no problem to have the cobuild.sh script depend on
> the patches in that directory.
>
> In fact, I've already started maintaining the patches there, starting from
> the next snapshot.
>
> % ls -l
> total 148
> -rw-r--r--    1 karrde   karrde       1043 Apr  4 10:58
> fltk-1.1.4-linux-patch.diff
> -rw-r--r--    1 karrde   karrde      14274 Apr  4 11:01
> fltk-1.1.4-winnt.patch.diff
> -rw-r--r--    1 karrde   karrde     123673 Apr  6 15:21 linux
>
>> If this is verified I would like to upload cobuild.sh to the wiki-page
>> to
>> document the build process.
>
> No need to upload files to the Wiki, just send me a patch.
>
> --
> Dan Aloni
> da...@co...
>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAdQlonwJBIFTVIqwRAm+eAJ9BVDiojp2T/ScWbN8fMAs/q0EHRACfS5hU
jeUhYgRwZaSOOjD5P4+PekU=
=Pko5
-----END PGP SIGNATURE-----