public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 1.7-58 with windows 2008
Date: Fri, 11 Mar 2016 06:38:00 -0000	[thread overview]
Message-ID: <loom.20160311T072725-366@post.gmane.org> (raw)
In-Reply-To: <CAPCR6Q15uhpvdH=rTHfXxaNK=+5y3-rF4ZSqvLGe=HOMGCEMSw@mail.gmail.com>

Rashi Singhal writes:
> Hello.
> 
> Please help me in resolving below compilation error:
> I am compiling Cygwin 1.7.0.58
> 
> make[5]: Leaving directory
> `/cygwin-1.7.0-58/i686-pc-cygwin/winsup/w32api/lib/directx'
> make[4]: Leaving directory `/cygwin-1.7.0-58/i686-pc-
cygwin/winsup/w32api/lib'
> make[3]: Leaving directory `/cygwin-1.7.0-58/i686-pc-
cygwin/winsup/w32api'
> make[3]: Entering directory `/cygwin-1.7.0-58/i686-pc-
cygwin/winsup/cygwin'
> g++ -L/cygdrive/c/cygwin/cygwin-1.7.0-58/i686-pc-cygwin/winsup
> -L/cygdrive/c/cygwin/cygwin-1.7.0-58/i686-pc-cygwin/winsup/cygwin
> -L/cygdrive/c/cygwin/cygwin-1.7.0-58/i686-pc-cygwin/winsup/w32api/lib
> -isystem /cygdrive/c/cygwin/cygwin-1.7.0-58/winsup/include -isystem
> /cygdrive/c/cygwin/cygwin-1.7.0-58/winsup/cygwin/include -isystem
> /cygdrive/c/cygwin/cygwin-1.7.0-58/winsup/w32api/include
> -B/cygdrive/c/cygwin/cygwin-1.7.0-58/i686-pc-cygwin/newlib/ -isystem
> /cygdrive/c/cygwin/cygwin-1.7.0-58/i686-pc-cygwin/newlib/targ-include
> -isystem /cygdrive/c/cygwin/cygwin-1.7.0-58/newlib/libc/include    -c
> -DHAVE_CONFIG_H  -g -O2 -MMD  -Werror -fmerge-constants -ftracer
> -Wall -Wstrict-aliasing -Wwrite-strings -fno-common -pipe -fbuiltin
> -fmessage-length=0  -I.
> -I/cygdrive/c/cygwin/cygwin-1.7.0-58/winsup/cygwin
> -I/cygdrive/c/cygwin/cygwin-1.7.0-58/winsup/w32api/include
> -I../../.././winsup/cygwin/config/i386
> -I/usr/lib/gcc/i686-pc-cygwin/3.4.4/include -fno-rtti -fno-exceptions
> -o ./_cygwin_crt0_common.o
> ../../.././winsup/cygwin/lib/_cygwin_crt0_common.cc
> 
> make[3]: *** [_cygwin_crt0_common.o] Error 127
> make[3]: Leaving directory `/cygwin-1.7.0-58/i686-pc-
cygwin/winsup/cygwin'
> make[2]: *** [cygwin] Error 1
> make[2]: Leaving directory `/cygwin-1.7.0-58/i686-pc-cygwin/winsup'
> make[1]: *** [all-target-winsup] Error 2
> make[1]: Leaving directory `/cygwin-1.7.0-58'
> make: *** [all] Error 2
> 
> Please give some clue what could be missing

I don't know the answer to your question.  But it appears you might be 
building in the same directory that holds the Cygwin source.  That won't 
work.  You should be following the recipe in the FAQ, located here...
https://cygwin.com/faq.html#faq.programming.building-cygwin

Note that the list of required build tools shown there may be a little 
different for such an old release, so beware.  But the main point is to 
set up a build directory like /oss, with subdirectories /oss/build, 
/oss/install, and /oss/src.  What I tend to do is define a symbolic link 
/oss/src that points at the directory containing the Cygwin source tree, 
/cygdrive/c/cygwin/cygwin-1.7.0-58 in your case.  Then cd to /oss/build 
and run configure and make like the FAQ entry describes.  Good luck!

..mark


--
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:[~2016-03-11  6:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  8:44 Rashi Singhal
2016-02-17  9:09 ` Marco Atzeri
2016-02-22  9:50 ` Rashi Singhal
2016-02-22 11:21   ` Marco Atzeri
2016-02-23  3:34   ` Rashi Singhal
2016-02-23 14:01     ` Marco Atzeri
2016-03-04 16:40     ` Rashi Singhal
2016-03-09  8:00       ` Rashi Singhal
2016-03-09  8:16         ` Marco Atzeri
     [not found]         ` <CAPCR6Q2GdXd=EF7iAdP+xYT7UomLefLKgDm=be0oD=Wh64T_-g@mail.gmail.com>
2016-03-11  2:40           ` Rashi Singhal
2016-03-11  6:38             ` Mark Geisert [this message]
2016-03-17 11:19             ` Rashi Singhal
2016-03-17 11:47               ` Marco Atzeri
2016-03-18 16:15               ` Peter A. Castro
     [not found]                 ` <CAPCR6Q32VQeQLLjOC6t5UNs-AVtHYC_Er1ETdZHtYifbD6j3rA@mail.gmail.com>
     [not found]                   ` <alpine.LNX.2.00.1603231447150.6583@ming.fruitbat.org>
2016-03-24  4:20                     ` Fwd: " Rashi Singhal
2016-03-24 19:29                       ` Warren Young
2016-03-24 19:36                         ` Warren Young
2016-03-25  5:38                       ` Fwd: " Mark Geisert
2016-03-28  9:08                       ` Rashi Singhal
2016-03-28 10:50                         ` Andrey Repin
2016-03-28 11:06                           ` Rashi Singhal
2016-03-28 14:30                             ` Erik Soderquist
2016-03-29  2:47                       ` Rashi Singhal
  -- strict thread matches above, loose matches on Subject: below --
2016-02-17  5:53 Rashi Singhal
2016-02-17  6:50 ` Larry Hall (Cygwin)

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=loom.20160311T072725-366@post.gmane.org \
    --to=mark@maxrnd.com \
    --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).