Re: cygwin Compile of NetBSD 1.6

2003-02-03 Thread Max Bowsher
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 probably biting off
>> more than you can chew, given your current level of knowledge (based
>> on the questions you have asked). Yet you practically accuse him of
>> witholding information.

> Sorry, not trying to be rude to Chris or you,

I never suspected deliberate intent to be rude. Just wanted to let you know
that your message could be read in that way.

> infact I've appreciated
> your help. Am I biting off more then I can chew? Sure, that's the fun
> of it :) Am I frustrated, not at all! This is for fun, not profit...
>
> 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.

Rude? No. Short and to the point, yes. A little blunt, maybe.

> Look, I'm not interested in a "flame" war with the Cygwin list. If my
> questions are inappropriate, simply tell me and/or ignore them as well
> as me.  Is that so hard to do? Mailing Lists are for questions. If
> they are not the appropriate questions for the list, dont engage.

Ok, Ok! No need to get wound up. Questions are always welcome here, so long
as they have at least a little bit to do with Cygwin.


Max.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: cygwin Compile of NetBSD 1.6

2003-02-03 Thread Christos Dritsas
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
benefit from his knowledge, not anyones ego.
   


That's cgf for ya ::-) Only kidding Chris '-)

 

I dont expect anyone to have all the answers, or even one answer.

Look, I'm not interested in a "flame" war with the Cygwin list. If my
questions are inappropriate, simply tell me and/or ignore them as well
as me.  Is that so hard to do? Mailing Lists are for questions. If they
are not the appropriate questions for the list, dont engage.
   


The link Vince Hoffman posted in a previous message is very interesting.
I've just read it :-) And should give you much help in this task. If you've
never done anything like this before, just remember to read all of the
README and INSTALL files in the source(tm) 'cause you'll need to build quite
a few cross-tools. If you need help with building a cross-gcc you might want
to look at the crossgcc ml (on sources.redhat.com) which may help.

 

Elfyn:

Thanks for the insight, I'm sure it will prove helpful on my voyage :) I 
just signed up for the crossgcc list, I'm sure that list will come in handy.

-Christos


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: cygwin Compile of NetBSD 1.6

2003-02-03 Thread Elfyn McBratney
> 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 his knowledge, not anyones ego.

That's cgf for ya ::-) Only kidding Chris '-)

> I dont expect anyone to have all the answers, or even one answer.
>
> Look, I'm not interested in a "flame" war with the Cygwin list. If my
> questions are inappropriate, simply tell me and/or ignore them as well
> as me.  Is that so hard to do? Mailing Lists are for questions. If they
> are not the appropriate questions for the list, dont engage.

The link Vince Hoffman posted in a previous message is very interesting.
I've just read it :-) And should give you much help in this task. If you've
never done anything like this before, just remember to read all of the
README and INSTALL files in the source(tm) 'cause you'll need to build quite
a few cross-tools. If you need help with building a cross-gcc you might want
to look at the crossgcc ml (on sources.redhat.com) which may help.

Good Luck!


Regards,

Elfyn McBratney
[EMAIL PROTECTED]
www.exposure.org.uk



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: cygwin Compile of NetBSD 1.6

2003-02-03 Thread Christos Dritsas
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/2001 - he did give me some good 
advice on what he had come across with pre NetBSD 1.6 and Cygwin.

Thanks for the link :)
-Christos


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: cygwin Compile of NetBSD 1.6

2003-02-03 Thread Christos Dritsas
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 chew, given your
current level of knowledge (based on the questions you have asked). Yet you
practically accuse him of witholding information.
 

Sorry, not trying to be rude to Chris or you, infact I've appreciated 
your help. Am I biting off more then I can chew? Sure, that's the fun of 
it :) Am I frustrated, not at all! This is for fun, not profit...

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 his knowledge, not anyones ego.

Secondly, you ask that others should do the hard work for you. That's a
guaranteed way to annoy people.


Dont want anyone to do any work, hard or easy for me, just asking 
questions. I appreciate any answers I get.

AFAIK, no one has ever done what you are trying to do before. You can't just
expect someone to have all the answers. Plus, none of the questions you have
asked so far are Cygwin-specific in any way.


I dont expect anyone to have all the answers, or even one answer.

Look, I'm not interested in a "flame" war with the Cygwin list. If my 
questions are inappropriate, simply tell me and/or ignore them as well 
as me.  Is that so hard to do? Mailing Lists are for questions. If they 
are not the appropriate questions for the list, dont engage.

Thanks again for the help from those of you who have given it.

-Christos

 



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




RE: cygwin Compile of NetBSD 1.6

2003-02-03 Thread Vince Hoffman
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



> -Original Message-
> From: Christos Dritsas [mailto:[EMAIL PROTECTED]]
> Sent: 03 February 2003 17:07
> To: [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 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
> >exercise.
> >  
> >
> Since you appear to be familiar with this, can you please 
> list the known 
> complex details of compiling NetBSD 1.6 under Cygwin. As 
> there is little 
> information to be found, that kind of a post would be some help.
> 
> Thank you,
> Christos
> 
> 
> 
> 
> 
> 
> 
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ:   http://cygwin.com/faq/
> 

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: cygwin Compile of NetBSD 1.6

2003-02-03 Thread Max Bowsher
> 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
>> exercise.

Christos Dritsas wrote:
> Since you appear to be familiar with this, can you please list the
> known complex details of compiling NetBSD 1.6 under Cygwin. As there
> is little information to be found, that kind of a post would be some
> help.

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 chew, given your
current level of knowledge (based on the questions you have asked). Yet you
practically accuse him of witholding information.

Secondly, you ask that others should do the hard work for you. That's a
guaranteed way to annoy people.

AFAIK, no one has ever done what you are trying to do before. You can't just
expect someone to have all the answers. Plus, none of the questions you have
asked so far are Cygwin-specific in any way.




Max.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: cygwin Compile of NetBSD 1.6

2003-02-03 Thread Shankar Unni


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:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: cygwin Compile of NetBSD 1.6

2003-02-03 Thread David Robinow
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 remote at best.
>>
>>This is not going to be a "fix a few problems and it works" type of
>>exercise.
>>  
>>
>Since you appear to be familiar with this, can you please list the known 
>complex details of compiling NetBSD 1.6 under Cygwin. As there is little 
>information to be found, that kind of a post would be some help.
  Please don't feed the animals.  You caught cgf in one of his good moods.  Let's not 
do anything to change that.
  It appears from your earlier posts that you are something of a novice with respect 
to the skills needed to do what you are attempting.  Nothing wrong with that but you 
should be prepared for an arduous process.  Many of the problems you are likely to run 
into are not really cygwin-specific so you will need to find appropriate places to ask 
for help.  I suggest you start with  http://sources.redhat.com/ml/crossgcc/
  Good luck.



__
The NEW Netscape 7.0 browser is now available. Upgrade now! 
http://channels.netscape.com/ns/browsers/download.jsp 

Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: cygwin Compile of NetBSD 1.6

2003-02-03 Thread Christos Dritsas
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 problems and it works" type of
exercise.
 

Since you appear to be familiar with this, can you please list the known 
complex details of compiling NetBSD 1.6 under Cygwin. As there is little 
information to be found, that kind of a post would be some help.

Thank you,
Christos







--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: cygwin Compile of NetBSD 1.6

2003-02-02 Thread Christopher Faylor
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
>>>"cc" comand.  Without changing anything in the build scripts, is there
>>>an easy way to tell the Cygwin bash enviornment to recognize "cc" as
>>>"gcc"?  I did attempt to use a name-value pair in the bash enviornment
>>>(as per the bash man page - "CC=C:\cygwin\bin\gcc.exe"), but it did not
>>>work for me.
>>
>>You can create a symbolic link from gcc to cc:
>>
>>$ cd /bin && ln -s gcc cc
>
>Or find out why it is finding a cc at all, and stop it.  Run "which cc"
>to find out where the cc is, if it is in your PATH.  If that doesn't
>find anything, then hack build.sh to preserve config.log, and check
>that.

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
exercise.

cgf

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: Cygwin Compile of NetBSD 1.6

2003-02-02 Thread Max Bowsher
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, is
>> there an easy way to tell the Cygwin bash enviornment to recognize
>> "cc" as "gcc"? I did attempt to use a name-value pair in the bash
>> enviornment (as per the bash man page - "CC=C:\cygwin\bin\gcc.exe"),
>> but it did not work for me.
>
> You can create a symbolic link from gcc to cc:
>
> $ cd /bin && ln -s gcc cc

Or find out why it is finding a cc at all, and stop it.
Run "which cc" to find out where the cc is, if it is in your PATH.
If that doesn't find anything, then hack build.sh to preserve config.log,
and check that.

Max.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: Cygwin Compile of NetBSD 1.6

2003-02-02 Thread Elfyn McBratney
> 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 to tell the Cygwin bash enviornment to recognize "cc" as "gcc"? 
> I did attempt to use a name-value pair in the bash enviornment (as per 
> the bash man page - "CC=C:\cygwin\bin\gcc.exe"), but it did not work for 
> me.

You can create a symbolic link from gcc to cc:

$ cd /bin && ln -s gcc cc


Regards,

Elfyn McBratney
[EMAIL PROTECTED]
www.exposure.org.uk


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: Cygwin Compile of NetBSD 1.6

2003-02-02 Thread Christos Dritsas
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 gcc... cc
checking for C compiler default output... configure: error: C 
compiler cannot create executables

ERROR: configure of nbmake failed
*** BUILD ABORTED ***

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 to tell the Cygwin bash enviornment to recognize "cc" as "gcc"? 
I did attempt to use a name-value pair in the bash enviornment (as per 
the bash man page - "CC=C:\cygwin\bin\gcc.exe"), but it did not work for 
me.

Any pointers would be apprecitated - thank you,
Christos



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: Cygwin Compile of NetBSD 1.6

2003-02-01 Thread Max Bowsher
> 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 build
>> stuff in /tmp, or somewhere, does it?

Christos Dritsas wrote:
> Not too sure, here is the relevent code from the build.sh script
> though: 
> 
> # Build bootstrap nbmake if needed.
> if $do_rebuildmake; then
> $runcmd echo "===> Bootstrapping nbmake"
> tmpdir="${TMPDIR-/tmp}/nbbuild$$"

Aha. It does put it elsewhere.

> 
> $runcmd mkdir "$tmpdir" || bomb "cannot mkdir: $tmpdir"
> trap "cd /; rm -r -f \"$tmpdir\"" 0

And it removes it all when the script exits.

> I did also look for the config.log under $TOP/tools/make/ but found
> nothing.

Now you know why.


Max.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: Cygwin Compile of NetBSD 1.6

2003-02-01 Thread Christos Dritsas
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 it could not be created. This
build.sh doesn't locate the temporary build stuff in /tmp, or somewhere,
does it?
 

Not too sure, here is the relevent code from the build.sh script though:

# Build bootstrap nbmake if needed.
if $do_rebuildmake; then
   $runcmd echo "===> Bootstrapping nbmake"
   tmpdir="${TMPDIR-/tmp}/nbbuild$$"

   $runcmd mkdir "$tmpdir" || bomb "cannot mkdir: $tmpdir"
   trap "cd /; rm -r -f \"$tmpdir\"" 0
   $runcmd cd "$tmpdir"

   $runcmd env CC="${HOST_CC-cc}" CPPFLAGS="${HOST_CPPFLAGS}" \
   CFLAGS="${HOST_CFLAGS--O}" LDFLAGS="${HOST_LDFLAGS}" \
   "$TOP/tools/make/configure" \
   || bomb "configure of nbmake failed"
   $runcmd sh buildmake.sh || bomb "build of nbmake failed"

   make="$tmpdir/nbmake"
   $runcmd cd "$TOP"
   $runcmd rm -f usr.bin/make/*.o usr.bin/make/lst.lib/*.o
fi

I did also look for the config.log under $TOP/tools/make/ but found 
nothing.

Thanks
~Christos




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: Cygwin Compile of NetBSD 1.6

2003-02-01 Thread Max Bowsher
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 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 build stuff in /tmp, or somewhere,
does it?

Max.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Re: Cygwin Compile of NetBSD 1.6

2003-02-01 Thread Max Bowsher
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... /usr/bin/sh
>  checking for gcc... cc
>  checking for C compiler default output... configure: error: C
>  compiler cannot create executables

Check config.log


Max.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/




Cygwin Compile of NetBSD 1.6

2003-02-01 Thread iosphere
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
checking for C compiler default output... configure: error: C 
compiler cannot create executables

ERROR: configure of nbmake failed
*** BUILD ABORTED ***

Could this be a missing shared library? Searched about and found some 
references to this with similar postings, also found some reference to 
bash possibly having some trouble.

Wanted to know if anyone else has come arcoss this, or may point me in a 
direction I have not yet traveled.

Thank you for your time,
Christos


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/