public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Can you compile node.js under cygwin?
Date: Sat, 26 Oct 2019 21:16:00 -0000	[thread overview]
Message-ID: <d225bf1d-f16f-73a5-30db-9c9ed23952f8@SystematicSw.ab.ca> (raw)
In-Reply-To: <765cfcf8-1d6e-42ea-ed31-12296e9b23b2@cs.umass.edu>

On 2019-10-26 08:09, Eliot Moss wrote:
> On 10/25/2019 1:37 PM, Cary Lewis wrote:
>> I tried to clone the repo, and after running configure, then make I got
>> this error:
>>
>> make -C out BUILDTYPE=Release V=0
>>    touch 12396aa5d0c66cc1eba58d7550d4db5f74c0a51c.intermediate
>>
>> LD_LIBRARY_PATH=/home/clewis/node/out/Release/lib.host:/home/clewis/node/out/Release/lib.target:$LD_LIBRARY_PATH;
>>
>> export LD_LIBRARY_PATH; cd ../.; mkdir -p tools/msvs/genfiles; "mc
>> src/res/node_etw_provider.man -h tools/msvs/genfiles -r tools/msvs/genfiles"
>> /bin/sh: mc src/res/node_etw_provider.man -h tools/msvs/genfiles -r
>> tools/msvs/genfiles: No such file or directory
>> make[1]: *** [node_etw.target.mk:17:
>> 12396aa5d0c66cc1eba58d7550d4db5f74c0a51c.intermediate] Error 127
>> rm 12396aa5d0c66cc1eba58d7550d4db5f74c0a51c.intermediate
>> make: *** [Makefile:101: node] Error 2
> 
> This program's configure is not cygwin-aware, apparently.  It sees something
> that looks like Windows and it's heading toward msvs (Microsoft Visual Studio),
> a Windows program, not a cygwin program.
> 
> I tried configure --dest-os=linux, and that mostly worked, but assumes ELF
> binaries are being used, but cygwin uses PE, not ELF (so that Windows can
> run the binaries linked with the cygwin library / runtime).  So the openssl
> assembly files failed.  Using configure --dest-os=linux --openssl-no-asm got
> past that problem but fails when trying to find /usr/include/sys/syscall.h,
> someting not provided under cygwin.
> 
> I also tried not giving --dest-os (and it then wants to do the msvs stuff,
> i.e., it treats it as Windows) and --dest-os=posix (which is what uname -a
> reports under modern cygwin) to no avail.
> 
> So IMO node's configure needs to be adjusted, but how to do that correctly
> is beyond my knowledge or the time I can invest.

Teach configure to recognize and use system types i686/x86_64-unknown-cygwin and
build/host triplets i686/x86_64-pc-cygwin.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2019-10-26 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 17:38 Cary Lewis
2019-10-25 19:40 ` [cygwin] " Jason Pyeron
2019-10-26 14:09 ` Eliot Moss
2019-10-26 21:16   ` Brian Inglis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d225bf1d-f16f-73a5-30db-9c9ed23952f8@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).