public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Wild <themiwi@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Compiling cygwin1.dll
Date: Wed, 04 Jun 2014 19:19:00 -0000	[thread overview]
Message-ID: <CAALQ5rmPR3A2dSFiJp+Mq4xsgTB+Jp9z9EUqVevoFZdga0_AQw@mail.gmail.com> (raw)
In-Reply-To: <1819551279.20140604213213@yandex.ru>

On Wed, Jun 4, 2014 at 7:32 PM, Andrey Repin wrote:
> Greetings, Michael Wild!
>
>> You tell me. I just checked out the source and followed the
>> instructions as I said in my first message. When doing so, there is a
>> dependency and binutils gets built.
>
>> If the instructions are outdated, I did something obviously wrong, or
>> there is a better way, please let me know.
>
> I've used this script to rebuild it.
>
> --------------------------------------------------------
> #!/bin/sh
> SUITE_ROOT=/c/dev/sdc1/cygwin
> BUILD_PATH="$SUITE_ROOT/build"
> INSTALL_PATH="$SUITE_ROOT/install"
> BUILD_MODULE="$SUITE_ROOT/src${PWD##$BUILD_PATH}"
>
> {
> "$BUILD_MODULE/configure" -v --prefix="$INSTALL_PATH"
> LANG=C make
> } |& tee rebuild.log
> --------------------------------------------------------
>
> Checked out the repository into $SUITE_ROOT/src, recreated the necessary paths
> in $SUITE_ROOT/build and restarted the script from certain paths until I
> succeed in building required portions of suite. (I was mainly intersted in
> winsup.)

Hi Andrey Repin

Many thanks. So you are saying, you never used the top-level build
system? That would explain a lot. So it is just an iterative trial and
error process? Way to go...

Cheers

Michael

--
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:[~2014-06-04 19:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03  6:38 Michael Wild
2014-06-03 10:35 ` Andrey Repin
2014-06-03 12:58   ` Michael Wild
2014-06-03 16:08     ` Larry Hall (Cygwin)
2014-06-04 14:45       ` Michael Wild
2014-06-04 17:35         ` Andrey Repin
2014-06-04 19:19           ` Michael Wild [this message]
2014-06-04 20:05             ` Andrey Repin
2014-06-04 21:07               ` Christopher Faylor
2014-06-05  4:56                 ` Michael Wild

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=CAALQ5rmPR3A2dSFiJp+Mq4xsgTB+Jp9z9EUqVevoFZdga0_AQw@mail.gmail.com \
    --to=themiwi@gmail.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).