On Thu, 6 Oct 2005, Steve wrote:
I've had a lot more success with 2005Q3 packages compiling than the
previous release, although some fairly major things are still broken
(eg. apache2 and gcc).
Using 2005Q3 is not a good idea for DragonFly. That is the stable branch
that is mostly for security bug fixes and crucial build issues.
Because DragonFly is a new platform (especially for pkgsrc), the many
fixes can't easily be pulled up to the 2005Q3 branch (mostly due to lack
of volunteer time for that specifically).
Please consider using HEAD for pkgsrc (for now).
As for Apache: Go through the code looking for checks for FreeBSD and add
similar checks for DragonFly as appropriate. And this needs to be sent
upstream to apache.org also.
And for gcc, same thing.
It says:
Invalid configuration `i386-pc-dragonfly1': system `dragonfly1' not
recognized
Invalid configuration `i386-pc-dragonfly1': system `dragonfly1' not
recognized
Unrecognized host system name i386-pc-dragonfly1.
So go through the code and find references to FreeBSD and seek what is
appropriate for checking for DragonFly also. Share your patches with
gcc-patches or whatever is good for GCC. (It may be useful to look at
DragonFly's src/gnu/usr.bin/cc34 or other code for comparisons.)
Jeremy C. Reed
technical support & remote administration
http://www.pugetsoundtechnology.com/
