On Wed, Jun 4, 2014 at 11:07 PM, Christopher Faylor wrote:
> On Wed, Jun 04, 2014 at 11:55:32PM +0400, Andrey Repin wrote:
>>Greetings, Michael Wild!
>>
>>> Many thanks. So you are saying, you never used the top-level build
>>> system?
>>
>>I don't NEED to rebuild whole toolchain to begin with.
>
>
On Wed, Jun 04, 2014 at 11:55:32PM +0400, Andrey Repin wrote:
>Greetings, Michael Wild!
>
>> Many thanks. So you are saying, you never used the top-level build
>> system?
>
>I don't NEED to rebuild whole toolchain to begin with.
If you follow the instructions for checking out cygwin you shouldn't
Greetings, Michael Wild!
> Many thanks. So you are saying, you never used the top-level build
> system?
I don't NEED to rebuild whole toolchain to begin with.
And it takes about half an hour just to configure it on my system. Or at least
half an hour up to first error, which I'm unable to get muc
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 di
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, ple
On Tue, Jun 3, 2014 at 6:07 PM, Larry Hall (Cygwin) wrote:
> On 06/03/2014 08:57 AM, Michael Wild wrote:
>>
>> On Tue, Jun 3, 2014 at 12:32 PM, Andrey Repin wrote:
>>>
>>> Greetings, Michael Wild!
>>>
In order to pinpoint an error I'm trying to compile cygwin1.dll from
source following th
On 06/03/2014 08:57 AM, Michael Wild wrote:
On Tue, Jun 3, 2014 at 12:32 PM, Andrey Repin wrote:
Greetings, Michael Wild!
In order to pinpoint an error I'm trying to compile cygwin1.dll from
source following the instructions here:
My question is: do you actually need to rebuild it, or you ju
On Tue, Jun 3, 2014 at 12:32 PM, Andrey Repin wrote:
> Greetings, Michael Wild!
>
>> In order to pinpoint an error I'm trying to compile cygwin1.dll from
>> source following the instructions here:
>
> My question is: do you actually need to rebuild it, or you just need the debug
> symbols?
>
>> htt
Greetings, Michael Wild!
> In order to pinpoint an error I'm trying to compile cygwin1.dll from
> source following the instructions here:
My question is: do you actually need to rebuild it, or you just need the debug
symbols?
> https://cygwin.com/faq.html#faq.programming.building-cygwin. However
Dear all
In order to pinpoint an error I'm trying to compile cygwin1.dll from
source following the instructions here:
https://cygwin.com/faq.html#faq.programming.building-cygwin. However,
when building binutils, I trip over this error:
https://sourceware.org/ml/binutils/2014-02/msg00064.html. Acco
On Thu, Jan 15, 2004 at 12:15:15PM -0500, Igor Pechtchanski wrote:
>On Thu, 15 Jan 2004, Christopher Faylor wrote:
>> Nope. I routinely build cygwin with text mode mounts with no problems
>> at all. I don't know why you were having problems but we're certainly
>> not going to document a bug.
>
>T
On Thu, 15 Jan 2004, Christopher Faylor wrote:
> On Thu, Jan 15, 2004 at 11:52:51AM +0100, Gabriel SOUBIES wrote:
> >I finally managed to re-build Cygwin, and your hint helped me a lot!
> >The problem was that i was downloading the sources using Cygwin's CVS
> >on a machine where Cygwin had been i
On Thu, Jan 15, 2004 at 11:52:51AM +0100, Gabriel SOUBIES wrote:
>I finally managed to re-build Cygwin, and your hint helped me a lot!
>The problem was that i was downloading the sources using Cygwin's CVS
>on a machine where Cygwin had been installed in NT mode (not by me).
>Then I burned the sour
-
De : Nuno Ferreira [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 14 janvier 2004 20:46
À : Gabriel SOUBIES
Cc : Cygwin mailing list
Objet : RE: Problem compiling cygwin1.dll from CVS
On Ter, 2004-01-13 at 15:41, Gabriel SOUBIES wrote:
> Thanks for your reply.
> I moved everything under a dire
On Ter, 2004-01-13 at 15:41, Gabriel SOUBIES wrote:
> Thanks for your reply.
> I moved everything under a directory /CompilCygwin that I just created.
> Unfortunately, it didn't change anything, i get the same error...
Hi,
I had the original problem and solved it but forgot to share it with the
li
nvier 2004 16:21
A : Gabriel SOUBIES
Cc : [EMAIL PROTECTED]
Objet : RE: Problem compiling cygwin1.dll from CVS
Even though your /cygdrive mount is binary, I'm a bit wary of building
outside of the cygwin root. Try building in some directory under "/" (not
"/cygdrive/c&qu
-target-winsup] Error 2
>
> As you can see, there is a segmentation fault in the c++ -o cygwin0.dll
> command and I think this is where the problem lies.
>
> Thanks for your help...
>
> Gabriel
>
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTEC
Oups, forgot my Cygwin.def...
Here it is.
Gabriel
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part
de Igor Pechtchanski
Envoye : lundi 12 janvier 2004 18:57
A : Gabriel SOUBIES
Cc : [EMAIL PROTECTED]
Objet : RE: Problem compiling cygwin1.dll from CVS
ome!
> Thx
>
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part
> de Igor Pechtchanski
> Envoye : vendredi 26 decembre 2003 17:12
> A : Nuno Ferreira
> Cc : [EMAIL PROTECTED]
> Objet : Re: Problem compiling cygwin1.dll from CVS
>
anski
Envoye : vendredi 26 decembre 2003 17:12
A : Nuno Ferreira
Cc : [EMAIL PROTECTED]
Objet : Re: Problem compiling cygwin1.dll from CVS
On Fri, 26 Dec 2003, Nuno Ferreira wrote:
> Hi,
> while trying to find a problem with an application I'm using (that by
> the way was corre
On Fri, 26 Dec 2003, Nuno Ferreira wrote:
> Hi,
> while trying to find a problem with an application I'm using (that by
> the way was corrected by yesterday's snapshot) I tried to compile the
> DLL from CVS and it failed with this error:
> [snip]
> collect2: ld terminated with signal 11 [Segmentat
Hi,
while trying to find a problem with an application I'm using (that by
the way was corrected by yesterday's snapshot) I tried to compile the
DLL from CVS and it failed with this error:
c++ -L/usr/src/build-cygwin/i686-pc-cygwin/winsup
-L/usr/src/build-cygwin/i686-pc-cygwin/winsup/cygwin -L/usr/
Nope - still on 3.2-2
will upgrade and try again
thx!
Ronald
-Original Message-
From: Max Bowsher [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 16, 2002 7:52 PM
To: Ronald Landheer-Cieslak; [EMAIL PROTECTED]
Subject: Re: Wring winioctl.h used in compiling cygwin1.dll from CVS
Nope - still on 3.2-2
will upgrade and try again
thx!
Ronald
-Original Message-
From: Max Bowsher [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 16, 2002 7:52 PM
To: Ronald Landheer-Cieslak; [EMAIL PROTECTED]
Subject: Re: Wring winioctl.h used in compiling cygwin1.dll from CVS
Ronald Landheer-Cieslak <[EMAIL PROTECTED]> wrote:
> I was just trying to compile the Cygwin DLL, but couln'd because the
> winioctl.h from w32api was never included (using CVS sources): the one
> actually includes was the one of my Cygwin installation.
Are you using gcc-3.2-3 ?
It is supposed to
Hello y'all,
I was just trying to compile the Cygwin DLL, but couln'd because the
winioctl.h from w32api was never included (using CVS sources): the one
actually includes was the one of my Cygwin installation.
This is the command-line used for the file that didn't compile because one of the
de
26 matches
Mail list logo
