Elfyn McBratney wrote:
Not accusing anyone of witholding information. Just appeared that
he[Chris] may have come across this before with the responce that he
gave. A responce which was rude, but not a bother to me. If this issue
has been worked on before, I as well as all others interested, would
Vince Hoffman wrote:
If you're realy serious i found this rather old bunch of mails with a quick
google which could possibly help
http://netbsd.kpsws.com/cross-comp/maillist
Vince:
Thanks. I did actually get in contact with Andrew Gillham, the first
poster. Although the post is old - 01/29
Max Bowsher wrote:
Christos, I can see that you might be frustrated, but your post above is
somewhat rude. Firstly, Chris does not "appear to be familiar" with NetBSD
on Cygwin. He's simply commenting that the that trying to recompile a whole
OS and tools is probably biting off more than you can
Christopher Faylor wrote:
On Sun, Feb 02, 2003 at 07:03:20PM -
Or, even, just give up since the likelihood of actually being able to
build NetBSD under Cygwin with little or no knowledge of cross compilers
or symlinks or log files is remote at best.
This is not going to be a "fix a few probl
Christos wrote:
I am attempting to compile NetBSD 1.6 via Cygwin 1.3.19-1 (on Win2k)
by issuing the following command:
./build.sh -m shark -u -t
I get the following error:
$ ./build.sh -m shark -u -t
===> Bootstrapping nbmake
checking for sh... /usr/bin/sh
checking for gc
Max Bowsher wrote:
Please keep replies on the mailing list.
opps, gotta hit that cc button :)
The output you posted looks like a standard autoconf-type configure. I think
that the config.log should be created in the current working directory when
configure is executed. I can't imagine how i
6 matches
Mail list logo