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/
Re: cygwin Compile of NetBSD 1.6
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
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
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
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
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/
