public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cwilson@ee.gatech.edu>
To: Sebastien Barre <Sebastien.Barre@utc.fr>
Cc: Cygwin Mailing List <cygwin@sourceware.cygnus.com>
Subject: Re: Compiling Perl under b20.1
Date: Sun, 07 Mar 1999 22:26:00 -0000	[thread overview]
Message-ID: <36E3670E.E9C1EAAA@ece.gatech.edu> (raw)
In-Reply-To: <4.1.19990307151654.016ccf10@mail.club-internet.fr>

Sebastien Barre wrote:

> At 13:27 06/03/99 -0500, Charles Wilson wrote:
>
> >BTW, did you apply the patch to a
> >pristine copy of the source, or had you already applied the changes from Teun
> >Burgers (below)?
>
> No, from the pristine copy of course :) My perl is working quite right I
> guess, I just wanted to help you controlling your build package, so I
> started from the beginning, following your statements.

I was fairly sure that was the case, but it's best to eliminate the simple things
first.

> <snip>

> Therefore, I guess that this information

> *definitely* need a place in your build instructions : egcs 1.1.1 might be
> handy.
>

Okay. I'll update the build-kit soon.

> <snip>

> >However, I

> >don't see how including Mr. Burgers' fixes will hurt anything, so I'll go
> ahead an
> >add them to the "patch", unless anyone can think of a good reason not to.
>
> I tried, but was unable to find the relevant part to patch.
>

I found the relevant part, and have changed the build-kit to include this patch.
Even though it probably doesn't matter if you're using egcs-1.1.1.

>
> >> *) Furthermore, I'd just add that I had some problems while building perl
> >> if source files were extracted in a binary mounted partition. BUT I also
> >> read some testimony regarding the contrary (i.e. you need to mount it as
> >> binary) ! Therefore, It's just a hint, but if you experience some problems
> >> (sadly, I forgot to save the error messages), try different mount mode.
>
> >I extracted into a binary mounted partition. My *guess* is that you might have
> >used WinZip or somesuch to extract the source. If WinZip converted all
> >newlines to \013\010, AND the partition was mounted binary, then that
> would cause problems.
>
> Nope, I'm aware of the Winzip problem, and I'm taking care of that, by
> systematically using tar / gzip :)

Well, then I'm stumped. I don't know what the *build* problem is (or even if there
is one, after applying all these patches) under text / binary mounts. *make test*
problems are a whole different kettle of fish....continued in next message.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: Charles Wilson <cwilson@ee.gatech.edu>
To: Sebastien Barre <Sebastien.Barre@utc.fr>
Cc: Cygwin Mailing List <cygwin@sourceware.cygnus.com>
Subject: Re: Compiling Perl under b20.1
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <36E3670E.E9C1EAAA@ece.gatech.edu> (raw)
Message-ID: <19990331194500.wZgBtnrh8vZCpC6my9yYDSAgOIWPy7k0xUmAe9qzGns@z> (raw)
In-Reply-To: <4.1.19990307151654.016ccf10@mail.club-internet.fr>

Sebastien Barre wrote:

> At 13:27 06/03/99 -0500, Charles Wilson wrote:
>
> >BTW, did you apply the patch to a
> >pristine copy of the source, or had you already applied the changes from Teun
> >Burgers (below)?
>
> No, from the pristine copy of course :) My perl is working quite right I
> guess, I just wanted to help you controlling your build package, so I
> started from the beginning, following your statements.

I was fairly sure that was the case, but it's best to eliminate the simple things
first.

> <snip>

> Therefore, I guess that this information

> *definitely* need a place in your build instructions : egcs 1.1.1 might be
> handy.
>

Okay. I'll update the build-kit soon.

> <snip>

> >However, I

> >don't see how including Mr. Burgers' fixes will hurt anything, so I'll go
> ahead an
> >add them to the "patch", unless anyone can think of a good reason not to.
>
> I tried, but was unable to find the relevant part to patch.
>

I found the relevant part, and have changed the build-kit to include this patch.
Even though it probably doesn't matter if you're using egcs-1.1.1.

>
> >> *) Furthermore, I'd just add that I had some problems while building perl
> >> if source files were extracted in a binary mounted partition. BUT I also
> >> read some testimony regarding the contrary (i.e. you need to mount it as
> >> binary) ! Therefore, It's just a hint, but if you experience some problems
> >> (sadly, I forgot to save the error messages), try different mount mode.
>
> >I extracted into a binary mounted partition. My *guess* is that you might have
> >used WinZip or somesuch to extract the source. If WinZip converted all
> >newlines to \013\010, AND the partition was mounted binary, then that
> would cause problems.
>
> Nope, I'm aware of the Winzip problem, and I'm taking care of that, by
> systematically using tar / gzip :)

Well, then I'm stumped. I don't know what the *build* problem is (or even if there
is one, after applying all these patches) under text / binary mounts. *make test*
problems are a whole different kettle of fish....continued in next message.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  reply	other threads:[~1999-03-07 22:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-04 18:06 Allan Peda
1999-03-04 20:29 ` How can I get off of this list? Ed Peddycoart
1999-03-31 19:45   ` Ed Peddycoart
     [not found] ` < 36DF49C5.BDE486B0@interport.net >
1999-03-05  8:06   ` Compiling Perl under b20.1 Sebastien Barre
1999-03-05 13:13     ` Charles Wilson
     [not found]       ` < 36E048F5.9B384A50@ece.gatech.edu >
1999-03-06  2:49         ` Sebastien Barre
1999-03-06 10:27           ` Charles Wilson
     [not found]             ` < 36E1739A.BEC6F38C@ece.gatech.edu >
1999-03-07 15:33               ` Sebastien Barre
1999-03-07 22:26                 ` Charles Wilson [this message]
1999-03-31 19:45                   ` Charles Wilson
1999-03-31 19:45                 ` Sebastien Barre
1999-03-31 19:45             ` Charles Wilson
1999-03-31 19:45           ` Sebastien Barre
1999-03-31 19:45       ` Charles Wilson
1999-03-31 19:45     ` Sebastien Barre
1999-03-31 19:45 ` Allan Peda
1999-03-05  6:22 Steven Zeil
1999-03-31 19:45 ` Steven Zeil
1999-03-06 10:41 Earnie Boyd
1999-03-06 12:07 ` Charles Wilson
     [not found]   ` < 36E18AF6.A967D7DA@ece.gatech.edu >
1999-03-07 15:33     ` Sebastien Barre
1999-03-07 23:19       ` Charles Wilson
     [not found]         ` < 36E37A18.A15F8524@ece.gatech.edu >
1999-03-08  5:43           ` Sebastien Barre
1999-03-31 19:45             ` Sebastien Barre
1999-03-31 19:45         ` Charles Wilson
1999-03-08  0:07       ` Charles Wilson
     [not found]         ` < 36E38547.482A019A@ece.gatech.edu >
1999-03-08  5:43           ` Sebastien Barre
1999-03-31 19:45             ` Sebastien Barre
1999-03-31 19:45         ` Charles Wilson
1999-03-31 19:45       ` Sebastien Barre
1999-03-31 19:45   ` Charles Wilson
1999-03-31 19:45 ` Earnie Boyd
1999-03-07 18:53 Earnie Boyd
1999-03-31 19:45 ` Earnie Boyd

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=36E3670E.E9C1EAAA@ece.gatech.edu \
    --to=cwilson@ee.gatech.edu \
    --cc=Sebastien.Barre@utc.fr \
    --cc=cygwin@sourceware.cygnus.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).