Christos Dritsas wrote:
> 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
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
> 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
> benefit from h
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
[EMAIL PROTECTED]
> Subject: Re: cygwin Compile of NetBSD 1.6
>
>
> 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
> Christopher Faylor wrote:
>> 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 problems and it works" type of
>
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.
Or wait! Maybe he can recompile Windows with Cygwin and run it on Linux!
Yeah!
--
Unsubscribe info:
Christos Dritsas <[EMAIL PROTECTED]> wrote:
>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 remot
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
On Sun, Feb 02, 2003 at 07:03:20PM -, Max Bowsher wrote:
>Elfyn McBratney wrote:
>>>So, what appears to be happening is that the build.sh script is
>>>recoginizing "cc" when checking for "gcc". Cygwin does not appear to
>>>recognize "cc" as a compiler on it - attempted test compiles with the
>
Elfyn McBratney wrote:
>> So, what appears to be happening is that the build.sh script is
>> recoginizing "cc" when checking for "gcc". Cygwin does not appear to
>> recognize "cc" as a compiler on it - attempted test compiles with the
>> "cc" comand. Without changing anything in the build scripts,
> So, what appears to be happening is that the build.sh script is
> recoginizing "cc" when checking for "gcc". Cygwin does not appear to
> recognize "cc" as a compiler on it - attempted test compiles with the
> "cc" comand. Without changing anything in the build scripts, is there an
> easy way
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:
>> 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 it could
>> not be created. This build.sh doesn't locate the temporary bu
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
Christos Dritsas wrote:
> Hi Max:
Please keep replies on the mailing list.
> The funny thing is I find no config.log anywhere. I did a search for
> it and it is not created, maybe this is part of my problem?
The output you posted looks like a standard autoconf-type configure. I think
that the co
iosphere wrote:
> I am attempting to compile NetBSD 1.6 via Cygwin 1.3.19-1 (on Win2k)
Ambitious!
> 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..
Good Day,
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 gcc... cc
19 matches
Mail list logo
