Re: META: Fix the signup procedure?
On Thu, Aug 12, 2021 at 12:36:12PM +0200, Valerio Messina wrote: >On 8/11/21 1:26 PM, Russell VT via Cygwin wrote: >>Can one of you powerful folks, please, fix the signup approvals and make it >>a bit more difficult to signup and account that is "allowed" to post on >>this list? > >as now the subscribe procedure is a simple: >0) open the web page: https://cygwin.com/mailman/listinfo/cygwin/ >1) fill form with name, email and pass >2) press the Subscribe button >3) receive a confirmation mail >4) follow the link in the mail >5) press the subscribe button in the new web page >all steps are easily script-able with 'curl' >So in my opinion first thing to do is to add a CAPTCHA [1] in the step 1 You can post to this list without subscribing so this wouldn't accomplish anything besides annoying people who want to subscribe. >I tried to contact the list admin sent from IP: 8.43.85.97 >that is asking for removal of spammers once we >received every spam, but spamming continue. That email address has nothing (or at least very little) to do with cygwin.com / sourceware.org. The right address is "postmaster", which is monitored by me. That said, I sure do not want to hear from "helpful" people pointing out spam. I monitor multiple lists for spam, block offending parties, and generate rules for spamassassin to stop similar messages from coming through. I see a lot more spam than anyone here and there's no reason to have someone add to the load by pointlesly showing me more. >I also noted a big increase in spam directed to my email, once I made >a post to the list. This is probably related to the fact the list >archive is freely available to web spiders at: >https://cygwin.com/pipermail/cygwin/ >with email sender visible as first line once you open an mail. >So second action to do is report the 'name' of sender but not the >email in those pages, or at least blacken the domain part @domain.tld We used to munge email addresses in a previous version of the mailing list but it was decided to stop doing so a couple of years ago when we moved to a new server / new mailing list software. The bottom line is that we're all volunteers here. It's unlikely that anyone is going to offer up more of their time to customize the tried-and-true mailing list software used by sourceware.org / cygwin.com / gcc.gnu.org. If the small amount of spam seen here bothers you then please don't contribute to it by publicly remarking on it. Unsubscribing is the best way to not see any more spam from the cygwin mailing list. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: META: Fix the signup procedure?
On Wed, Aug 11, 2021 at 04:26:18AM -0700, Russell VT wrote: >List Admins - > >Can one of you powerful folks, please, fix the signup approvals and >make it a bit more difficult to signup and account that is "allowed" to >post on this list? The cygwin list has been open for around 23 years or so. Making the list subscriber-only (which seems to be what you're asking for) raises the barrier to asking questions and impedes the purpose of a "help" mailing list. Moderation is an option but I doubt anyone really wants to moderate every message here. cgf -- cygwin.com/sourceware.org administrator -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Test message - please ignore
On Sat, May 01, 2021 at 11:47:46AM +1000, Duncan Roe wrote: >Test ezmlm replacement Please don't send test messages. If you have something to say, send the message. That will show you if your mail made it through or not. If you don't have anything to post about then there's no need for hundreds of people to see your test. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin.com address down
On Sat, Jan 02, 2021 at 06:00:32PM +, Peter Rice wrote: >I tried installing cygwin on a new Windows 10 system yesterday and it >failed to find any mirror sites. > >I can see www.cygwin.com to start the download, but then everything >points to cygwin.com and all those links fail (but work when I add >'www.' to the URL) > >For example: The "mirrors" left menu link to >https://cygwin.com/mirrors.html fails but >https://www.cygwin.com/mirrors.html works > >I will keep trying to see if it is back - or maybe everything should >just be pointing to the www.cygwin.com address. https://www.isitdownrightnow.com/cygwin.com.html -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Country Of Origin Verification - 8944
On Thu, Jun 11, 2020 at 11:24:09AM -0600, Brian Inglis wrote: >On 2020-06-11 10:07, Watson, Christian M. (GRC-V000)[Peerless Technologies >Corp.] via Cygwin wrote: >> My name is Christian Watson and I am a Supply Chain Risk Management >> Coordinator at NASA Glenn Research Center As such, I ensure that all NASA >> Headquarter IT purchase requests comply with Section 514 of the Consolidated >> Appropriations Act, 2018, Public Law 115-141 (amended), enacted February 28, >> 2018. To do so, the country of origin information must be obtained from the >> company that develops, produces, manufactures, or assembles the product(s). >> Specifically, identify the country where each of the following products were >> developed, manufactured, and assembled: >> >> * TightVNC 2.8.27 >> >> Additionally, if the country of origin is outside the United States, please >> provide any information you may have stating that testing is performed in >> the United States prior to supplying products to customers. >> Lastly, if available, please identify all authorized distributors of the >> product in question. > >This is the second email like this you have sent to the Cygwin mailing list: >if you are going to send a bunch of these to the Cygwin mailing list, you >should >save yourself time and energy, and list all the Cygwin packages in one email, >which may receive no response, unless you are spam blocked. ^^^ ...which is a very good possibility if this proves to be write-only email. cgf -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Mailing list Digest: Inconvenient format change: no more thread grouping, long message names
On Wed, Jun 03, 2020 at 04:33:42PM +, Vermessung AVT - Wolfgang Rieger wrote: >Why was this change made? sourceware.org migrated to new hardware and new, supported, "mailman" mailing list software few months ago. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Two naive questions
On Fri, Apr 24, 2020 at 11:58:26AM -0700, Stephen Carrier wrote: >On Thu, Apr 23, 2020 at 03:13:12PM -0400, Christopher Faylor wrote: >> To summarize: You can click on the mailto link of any message in the >> archive and it will invoke your email client with the proper In-Reply-To >> set. That will allow you to reply to the sender of the message and >> maintain proper threading. If you want to send to the list, replace the >> "To" with the email address of the list. > >Yes! In this message: > >https://cygwin.com/pipermail/cygwin/2020-April/244568.html > >I said that your suggestion was a good one. Maybe you missed it? >That's when I was replying to you! Ah, many apologies for not following my own advice. I'm sorry to have made you spend time responding to my own confusion. Just to be definitive: The old mailing list software *did* allow retrieving old messages via email the new one does not. >>If none of this meets your needs then maybe some of the other sites >>that archive the cygwin list will have something more to your liking. > >If you don't mind, I'll continue to participate in the list, which I >like very much the way it is. Have you confused me with someone else? I was not in any way suggesting that you go elsewhere to discuss things. I was just pointing out that cygwin.com is not the only place that *archives* email and was suggesting that possibly one of the other sites out there might offer what you're looking for. It's probably unlikely but I thought I'd mention it. https://marc.info/?q=about http://gmane.io/ cgf -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Two naive questions
On Thu, Apr 23, 2020 at 03:13:12PM -0400, Christopher Faylor wrote: >Information provided information here: Or, even just "Information provided here:" -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Two naive questions
On Thu, Apr 23, 2020 at 09:49:34AM -0700, Stephen Carrier wrote: >On Wed, Apr 22, 2020 at 12:57:50PM +0300, Andrey Repin wrote: >>You can ask list management software to resend past messages. I don't >>recall specifics, and given the recent change, they may be entirely >>obsolete. You can check https://www.list.org/ for directions. > >As I commented upthread (Monday) I have seen instructions on how to >recall messages. I tried them, and they did not work. I tried again >more recently, and the instructions did not work, and I received bounce >messages to the effect that the request was not understood. I also >commented above that I had looked at the mailman documentation for >which you provide a link, and did not find any method described for >recalling messages. Apparently you're not reading the whole cygwin mailing list thread on this subject: https://cygwin.com/pipermail/cygwin/2020-April/thread.html To reiterate, cygwin.com's hosting site "sourceware.org" went through a hardware and software change in March. If you're attempting to use instructions from before the move to new hardware and different mailing list software then they won't work. >If you think I am mistaken, please find the information on how to do this >and provide a specific link. Providing a link to the main documentation >page and suggesting that others go looking is to send them on a wild-goose >chase aka waste of time. > >It would be a useful feature, I agree, and if I simply failed to find >what I was looking for, I would welcome correction. Information provided information here: https://cygwin.com/pipermail/cygwin/2020-April/244545.html https://cygwin.com/pipermail/cygwin/2020-April/244546.html To summarize: You can click on the mailto link of any message in the archive and it will invoke your email client with the proper In-Reply-To set. That will allow you to reply to the sender of the message and maintain proper threading. If you want to send to the list, replace the "To" with the email address of the list. I am aware that some people may find this incredibly daunting but that's what's available given the software that we're using. Read the thread for why we're using the mailman2 software. You can download the archive by going to, e.g., https://cygwin.com/pipermail/cygwin/ and clicking on the "Downloadable version" for the time period that you need. It will be a gzipped mbox-formatted text archive. If none of this meets your needs then maybe some of the other sites that archive the cygwin list will have something more to your liking. cgf -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Mailing list musings (was Re: Two naive questions)
On Tue, Apr 21, 2020 at 12:33:59PM -0600, Brian Inglis wrote: >On 2020-04-20 14:14, Christopher Faylor wrote: >> On Mon, Apr 20, 2020 at 11:59:08AM -0600, Brian Inglis wrote: >>> The new server ml archive does not seem to offer the metadata available on >>> the >>> previous server and archive, and that is true of most archives that do not >>> allow >>> replies: probably a good way to reduce space required by 50-90%, from what >>> I can >>> see. >>> A subscribed user could provide you with the reply References header values. >> This is a text cut and paste from https://cygwin.com/pipermail/cygwin/ >> The Cygwin Archives >> You can get more information about this list. >> Archive View by:Downloadable version >> April 2020: [ Thread ] [ Subject ] [ Author ] [ Date ] [ >> Gzip'd Text 110 KB ] >> Notice the "Gzip'd Text ..."? >> That's the mbox formatted email archives. > >I imported them all into Thunderbird to be able to search locally, as all >archive search tools seem to be worse than any of the search sites in >determining relevance or providing *all* relevant results newest first, while >the builtin tools allow searching on header field combos, and there is always >grep/sed/awk thru the mozmsgs maildirs for the really fuzzy searches. > >Your previous reply was probably the best that can be done with pipermail >archives on mailman 2.1, although I am surprised you did not go to mailman 3 >with hyperkitty on the new servers. Only mailman2 is available right now. % dnf list 'mailman*' Last metadata expiration check: 0:00:49 ago on Tue 21 Apr 2020 08:10:25 PM GMT. Installed Packages mailman.x86_64 3:2.1.29-4.module_el8.0.0+34+0459d3d0 @AppStream Available Packages mailman-debuginfo.x86_64 3:2.1.29-4.module_el8.0.0+34+0459d3d0 base-debuginfo mailman-debugsource.x86_64 3:2.1.29-4.module_el8.0.0+34+0459d3d0 base-debuginfo As I said in a previous reply: On Sat, Apr 18, 2020 at 10:58:31PM -0400, Christopher Faylor wrote: >There have been a few threads with people complaining about the change >in some of the other sourceware lists but we're using the officially >supported solution for maintaining a mailing list on RHEL and that is >not going to change. The overseers discussed a couple of other alternatives to mailman2 + postfix like inbox and exim but, in the end, chose to stick with what was supported and most common. This is to avoid a situation from old sourceware incarnations where we limped along for twenty years using the barely supported/unsupported qmail+ezmlm combo (along with their companion replacement for bind). qmail and ezmlm were both amazing pieces of software but they were showing their age in the era of DMARC, DKIM, and SPF. Anyway, if another mailing list package becomes available then we'll look at it but we are letting things settle down after the major move of sourceware to new hardware and software. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Two naive questions
On Mon, Apr 20, 2020 at 02:44:41PM -0600, Bill Stewart wrote: >On Mon, Apr 20, 2020 at 2:09 PM Christopher Faylor wrote: >>With mailman, if you click on a message in the archives and then click >>on the email address at the top, your mail client of choice will be >>opened with correct "In-Reply-To" set. If you want to reply to the >>list then replace the "To" with the email address of the mailing list. >>You can also download the mailbox-formatted archive, read it with a >>client like "mutt" and reply that way. > >So it is _possible_, but not exactly user-friendly (you're presuming >that end-users even understand these instructions). What if a user is >limited to a web-based mail client, for example, and has no way to >access said options? (I think it goes without saying that a "use a >better mail client" response is not feasible, at least for some users, >in addition to possibly sounding a bit elitist.) So, there's a potential email client out there which doesn't allow you to change the To address. Sounds pretty limiting but I guess it's not too surprising. Anyway, I was just instructing in how this could be done, in case someone who knew what they were doing was interested. I wasn't saying "WRONG! Mailman is awesome as a message board!" -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Two naive questions
On Mon, Apr 20, 2020 at 11:59:08AM -0600, Brian Inglis wrote: >The new server ml archive does not seem to offer the metadata available on the >previous server and archive, and that is true of most archives that do not >allow >replies: probably a good way to reduce space required by 50-90%, from what I >can >see. >A subscribed user could provide you with the reply References header values. This is a text cut and paste from https://cygwin.com/pipermail/cygwin/ The Cygwin Archives You can get more information about this list. Archive View by:Downloadable version April 2020: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 110 KB ] Notice the "Gzip'd Text ..."? That's the mbox formatted email archives. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Two naive questions
On Mon, Apr 20, 2020 at 11:41:32AM -0600, Bill Stewart wrote: >On Mon, Apr 20, 2020 at 11:20 AM Stephen Carrier wrote: >>I think the OP's first question was asking how to effectively join an >>existing thread when one is browsing the recent archives and not >>subscribed to the list. >> >>Joining the list after seeing a question one would like to answer >>doesn't help, because the message you would like to respond to has >>already gone by. >> >>I think a good solution would be to get the message number from the web >>archive and request that a particular message be sent to you. Then you >>could respond to that message and join the thread properly. >> >>However, there doesn't seem to be a way to do that. I used to be >>notified how to retrieve messages I had missed (due to bouncing) but >>the method did not work. Furthermore, the mailman faq doesn't mention >>any way to do this. > >I would say that this is a side-effect of using a mailing list when >what's really being asked for is a discussion forum. > >A mailing list is convenient for self-subscription and replies, but >replying to a past message (one that's "already gone by" as stated >above) is not really possible (that I know of?). Starting a new >message to the list with an identical subject to an existing thread >doesn't reply to the existing thread but rather starts a new thread >with an identical subject (since the thread ID is different). With mailman, if you click on a message in the archives and then click on the email address at the top, your mail client of choice will be opened with correct "In-Reply-To" set. If you want to reply to the list then replace the "To" with the email address of the mailing list. You can also download the mailbox-formatted archive, read it with a client like "mutt" and reply that way. OTOH, most message boards have a way to freeze old discussions and discourage resurrecting dead threads. The archives obviously don't allow that so you might want to consider if your resurrection of an old discussion would really be appreciated. If the discussion is old it's probably best to start a new thread and maybe include a link to the archive. But, really, if you want to be part of an active discussion then join the mailing list. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Two naive questions
On Thu, Apr 16, 2020 at 08:21:56PM +, Fergus Daly wrote: >2. Since when the new look provided by >https://cygwin.com/pipermail/cygwin/ ? >Is there a way to default to the "legacy" look provided at, say, >https://sourceware.org/legacy-ml/cygwin/2019-04/ >but not obviously available today (even by changing 2019 to 2020 in the >line above)? (I've looked for what I had assumed would be a long >conversation on this change, but cannot find anything.) sourceware is now using an the mailman mailling list software which is what you see expressed in the "pipermail" link above. There have been a few threads with people complaining about the change in some of the other sourceware lists but we're using the officially supported solution for maintaining a mailing list on RHEL and that is not going to change. So, no, there is no way to go back to the previous behavior. cgf (sourceware administrator) -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Setup mirrors
On Mon, Mar 09, 2020 at 11:34:27PM +, Jon Turney wrote: >>Since then, a number of things gone wrong, including mailing list signature. > >We have Top Men working on it, right now. Huh? Wha? -- 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
Re: ezmlm warning (fixed)
The duplicate Sender header was mainly coming from announce-list resends. It was helpfully added by perl's Mail::Internet package. The mailing list software has been modified to delete incoming Sender header fields when it sees them which should result only one Sender: header in mail to the list. On Mon, May 06, 2019 at 04:02:55PM -0400, sourcemaster wrote: >Please use postmaster (cc'ed), not sourcemaster, for email issues. >See: RFC 822. > >On Mon, May 06, 2019 at 03:51:21PM -0400, Chris Wagner wrote: >>Maintainers, I have been getting numerous bounce warnings and spam >>holds on mail sent to me by the Cygwin list. The spam holds are due >>to protocol violations. This ezmlm warning is because of: 550 >>Messages should have one or no Sender headers, not 2. >> >>If the list software could be made more compliant or I could be >>informed about some loosened setting on my spam panel. >> >>Thanks. >> >> >> >>On 2019-05-06 2:22 pm, cygwin-help wrote: >>>Hi! This is the ezmlm program. I'm managing the >>>cygwin mailing list. >>> >>> >>>Messages to you from the cygwin mailing list seem to >>>have been bouncing. I've attached a copy of the first bounce >>>message I received. >>> >>>If this message bounces too, I will send you a probe. If the probe >>>bounces, >>>I will remove your address from the cygwin mailing list, >>>without further notice. >>> >>> >>>I've kept a list of which messages from the cygwin mailing list have >>>bounced from your address. >>> >>>Copies of these messages may be in the archive. >>>To retrieve a set of messages 123-145 (a maximum of 100 per request), >>>send an empty message to: >>> >>> >>>To receive a subject and author list for the last 100 or so messages, >>>send an empty message to: >>> >>> >>>Here are the message numbers: >>> >>> 216505 >>> 216503 >>> 216515 >>> 216521 >>> 216525 >>> 216526 >>> 216529 >>> 216533 >>> 216540 >>> 216556 >>> 216557 >>> 216558 >>> 216559 >>> 216560 >>> 216561 >>> 216563 >>> 216564 >>> 216562 >>> 216571 >>> 216574 >>> 216575 >>> 216583 >>> 216579 >>> 216585 >>> 216586 >>> 216580 >>> 216587 >>> 216588 >>> 216590 >>> 216582 >>> 216584 >>> 216591 >>> 216589 >>> 216581 >>> 216594 >>> 216595 >>> 216598 >>> 216599 >>> 216601 >>> 216602 >>> 216600 >>> 216603 >>> 216604 >>> 216614 >>> 216623 >>> 216616 >>> 216615 >>> 216618 >>> 216619 >>> 216620 >>> 216621 >>> 216622 >>> >>>--- Enclosed is a copy of the bounce message I received. >>> >>>Return-Path: <> >>>Received: (qmail 67289 invoked for bounce); 24 Apr 2019 18:35:31 - >>>Date: 24 Apr 2019 18:35:31 - >>>From: mailer-dae...@sourceware.org >>>To: cygwin-return-216505-@ >>>Subject: failure notice >>> >>>Hi. This is the qmail-send program at sourceware.org. >>>I'm afraid I wasn't able to deliver your message to the following >>>addresses. >>>This is a permanent error; I've given up. Sorry it didn't work out. >>> >>>: >>>User and password not set, continuing without authentication. >>> 69.64.57.52 failed after I sent the message. >>>Remote host said: 550 Messages should have one or no Sender >>>headers, not 2. >> -- 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
Re: Missing Message-Id header on forwarded email
On Wed, Dec 20, 2017 at 12:22:35PM -0500, cyg Simple wrote: >The cygwin-annou...@cygwin.com list forwards email to the >cygwin@cygwin.com list. That email is missing the Message-Id header. >My email provider, gmail.com, adds the header with a suffix indicating >that it was added by the provider. Should be fixed now but the message-id for cygwin will be different than the one for cygwin-announce. They shouldn't be the same because they aren't exactly the same message. And, the archiving software archives based on message-id. -- 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
Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
On Wed, Dec 14, 2016 at 09:15:46AM -0500, cyg Simple wrote: >On 12/10/2016 3:39 PM, Christopher Faylor wrote: >> On Wed, Nov 30, 2016 at 11:00:12AM -0500, Christopher Faylor wrote: >>> On Wed, Nov 30, 2016 at 10:55:49AM -0500, Frank Ch. Eigler wrote: >>>> cygsimple wrote: >>>>> See the description below of a problem that is occurring because of >>>>> DMARC rules in place by yahoo.com. Is there anything you can do for this? >>>> >>>> cgf, any chance of updating our copy of ezmlm-toaster etc.? >>>> Newer-than-2014 versions of ezmlm-idx seem to have some DMARC >>>> capabilities. >>> >>> I started looking at this when it came in. No ETA yet. >> >> Huh. I thought I sent an update about this but it vanished in the aether. >> >> I just turned on a new DMARC-aware version of ezmlm-send which rewrites >> the From address for any domain that is DMARC sensitive to something like: >> >> "User name via mailinglist <mailingl...@sourceware.org>" >> >> when the mail is broadcast to the mailing list. I would have done this >> sooner but my ezmlm skills were really rusty and I almost ran out of >> extremities to shoot. >> >> Please send any errors or issues encountered to overse...@sourceware.org. > >The issue continues. > >Here are the message numbers: > > 206020 > 206062 I sent the above on 12/10. Those messages were sent on 12/1 and 12/7 respectively. The change was not retroactive. -- 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
Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
On Mon, Dec 12, 2016 at 12:07:19PM +, Ian Lambert wrote: >On Sat, 12/10/16, Christopher Faylor ><cgf-use-the-mailinglist-ple...@sourceware.org> wrote: > I just turned on a > new DMARC-aware version of ezmlm-send which rewrites > the From address for any domain that is DMARC > sensitive to something like: > >... > Please send any > errors or issues encountered to overse...@sourceware.org. > > = = = > >It seems to have done away with the auto-signature helpful >links, and References, at least for my last reply. > >Problem reports: >FAQ: >Documentation: >Unsubscribe info: >and >References Should be fixed now. cgf -- 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
Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
On Wed, Nov 30, 2016 at 11:00:12AM -0500, Christopher Faylor wrote: >On Wed, Nov 30, 2016 at 10:55:49AM -0500, Frank Ch. Eigler wrote: >>cygsimple wrote: >>> See the description below of a problem that is occurring because of >>> DMARC rules in place by yahoo.com. Is there anything you can do for this? >> >>cgf, any chance of updating our copy of ezmlm-toaster etc.? >>Newer-than-2014 versions of ezmlm-idx seem to have some DMARC >>capabilities. > >I started looking at this when it came in. No ETA yet. Huh. I thought I sent an update about this but it vanished in the aether. I just turned on a new DMARC-aware version of ezmlm-send which rewrites the From address for any domain that is DMARC sensitive to something like: "User name via mailinglist <mailingl...@sourceware.org>" when the mail is broadcast to the mailing list. I would have done this sooner but my ezmlm skills were really rusty and I almost ran out of extremities to shoot. Please send any errors or issues encountered to overse...@sourceware.org. cgf
Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
On Wed, Nov 30, 2016 at 11:00:12AM -0500, Christopher Faylor wrote: >On Wed, Nov 30, 2016 at 10:55:49AM -0500, Frank Ch. Eigler wrote: >>cygsimple wrote: >>> See the description below of a problem that is occurring because of >>> DMARC rules in place by yahoo.com. Is there anything you can do for this? >> >>cgf, any chance of updating our copy of ezmlm-toaster etc.? >>Newer-than-2014 versions of ezmlm-idx seem to have some DMARC >>capabilities. > >I started looking at this when it came in. No ETA yet. I'm going to use start using a new version of ezmlm-send on Friday. It will rewrite the From addresses of any domain which wants to use DMARC. From what I've read, that should stop yahoo and gmail from complaining. cgf -- 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
Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
On Wed, Nov 30, 2016 at 10:55:49AM -0500, Frank Ch. Eigler wrote: >cygsimple wrote: > >> See the description below of a problem that is occurring because of >> DMARC rules in place by yahoo.com. Is there anything you can do for this? > >cgf, any chance of updating our copy of ezmlm-toaster etc.? >Newer-than-2014 versions of ezmlm-idx seem to have some DMARC >capabilities. fche, I read overseers. No need to clutter my personal inbox with this. I started looking at this when it came in. No ETA yet. cgf -- 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
Withdrawing from the project
As I mentioned in the cygwin mailing list: I'm withdrawing from the project. I'm sending a separate note here with information about the cygwin-apps part of this decision. The upset perl script lives in ~cygwin/setup. This is also a git repository. When you push to it, it updates the active version of upset so be careful. The companion Makefile which runs upset is also in this repository/directory. Scripts for keeping cygwin alive: /sourceware/infra/bin/check-cygwin-mirrors Keeps the mirror list alive, creates the mirrors web page, and mirrors list file. Check cygwin-admin crontab file for how it is run. Someone should change the crontab to have it send email to them. It used to notify me and I temporarily just changed it to sourcemas...@sourceware.org. /sourceware/infra/bin/cygssh Adds a new user when fed SSH key for upload access mail. I've been running this script as root. I don't remember why now. Presumably it can be run as the just-created cygwin-admin user. If this actually does need root you'll need to coordinate with overseers. If I missed something look in /sourceware/infra/bin or in the cygwin-admin crontab. I'd be happy to receive well wishes or answer questions about my decision in private email (me period cgf period cx) but please don't send me questions asking how to do something on sourceware.org or within cygwin itself. I'd like to make this a clean break. So long, farewell, auf wiedersehen, goodbye. cgf
Withdrawing from the project
In the last several months I've told various key players in the Cygwin project that I was thinking about withdrawing from the project. Today is the day that this becomes official. I was hoping that my final act for Cygwin would be to get it imported into git but it looks like that will be handled by someone else so that is no longer a gating factor. I'll be unsubscribing from all cygwin mailing lists right after sending this. I'll likely continue to use Cygwin but just as a user. If anyone is interested, I'm planning on redirecting my time by getting involved in the Android development community. Felly hir, a diolch am yr holl bysgod. cgf -- 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
Re: [ANNOUNCEMENT] Updated: xorg-server-1.15.1-4
On Mon, Jul 21, 2014 at 07:14:42PM +0200, Marco Atzeri wrote: On 21/07/2014 16:57, Matt D. wrote: to that should be up to date? most of the mirrors have a 24 hours cycle Actually, many mirrors update from sourceware.org every couple of hours. kernel.org is one example. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: The eternal uid issue
On Wed, Jul 23, 2014 at 08:08:07PM +0400, Andrey Repin wrote: Greetings, D. Boland! Cygwin security will be done for in the long run. Why not make the leap and show MS admins/developers how it should be done? You really think they are all idiots?... Like, really? Sure, why not. MS admins/developers are all idiots who are apparently supposed to be taught by Cygwin developers who have been getting it wrong for many years until being correct by the OP. To the OP: If you want to start a dialog, do research and ask questions. Don't just assume that you understand everything and can provide insight that no one else has thought of. cgf -- 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
Re: Some programs (vi, ssh) crash when screen buffer height is big
On Mon, Jul 21, 2014 at 12:32:34PM +, Nellis, Kenneth wrote: From: sous lesquels snip If you can't wait, then read the message using your browser and click on the Raw text link near the top. The first line will say something like From cygwin-return-191383-listarch-cygwin=... Note the message number 191383. Then you send an empty message to cygwin-get.191...@cygwin.com and it will mail you back the specified message. You can then reply to it and your reply will be threaded. Perfect, exactly what I was looking for. Agree it's not the most direct method, but then again solves all the situations I could think of requiring a physical email message that can be replied to. Thanks for the tip Ken! Glad to help. I'm thinking it should be dirt simple for the web site maintainer to add a hyperlink right on the message web page, perhaps under the Raw text link, which would say something like Request this message. It would simply be a mailto: link with the correct message number added. I'm thinking this could make life much easier for digest readers, like myself. In the example above, the link would be: a href=mailto:cygwin-get.191...@cygwin.com;Request this message/a The only trick would be inserting the proper message number. No, we're not going to change the way the web archive works. There is no easy way that the archiving software would know what the mailto: link would be. And, I'm not too interested in hacking at the archiver anyway. I'll say it again: Just add the In-Reply-To or References with the right Message-ID and you'll get threading. cgf -- 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
Reminder: Don't send html email and don't try to send private messages
I just got back from a couple days of vacation and had to clean out the spam traps. As is usual these days, the majority of the email there was not spam but was just was html-formatted. Anyone who showed up in the spam trap already got a message telling them not to do that but I thought I would send a reminder here too so that it shows up in the archives: sourceware.org/cygwin.com/gcc.gnu.org don't accept html-formatted email even if it includes a plain text component. https://sourceware.org/lists.html#html-mail There wasn't any attempt to email Corinna or Larry directly this time but I'll add the usual caveat against doing that here too. Private email is not going to work regardless of whether you html formatting or not. If either of those two notables wanted to communicate privately they will give you their private email addresses (if you're a maintainer you know how to get in touch privately if needed). https://cygwin.com/problems.html Please don't attempt to argue about the utility of html-formatted email since, other than me, the sysadmins for the site don't read this list and changing the policy would require every sysadmin to agree. -- 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
Re: [ITA] Git et al
On Sat, Jul 19, 2014 at 08:29:41AM +0100, Adam Dinwoodie wrote: I've still not been able to clone the Cygwin source code from CVS -- I've been testing by cloning the cygwin-apps repo Yaakov referenced above -- but the errors look like a version incompatibility, and I don't think there's much I can do about that. If someone who knows more about CVS and Git could take a look at the output and confirm that hypothesis, I'd be grateful: $ git cvsimport -v -d :pserver:anon...@cygwin.com:/cvs/src src Initialized empty Git repository in /home/add/test/.git/ Running cvsps... WARNING: malformed CVS version str: Server: WARNING: Your CVS client version: [Client: Concurrent Versions System (CVS) 1.12.13 (client/server)] and/or server version: [Server: ] are too old to properly support the rlog command. This command was introduced in 1.11.1. Cvsps will use log instead, but PatchSet numbering may become unstable due to pruned empty directories. cvs [log aborted]: reading from server: Connection reset by peer DONE; creating master branch fatal: refs/heads/origin: not a valid SHA1 fatal: master: not a valid SHA1 fatal: You are on a branch yet to be born checkout failed: 32768 As I say, the cvsimport of the cygwin-apps repo is going just fine, so I don't think this is a fundamental problem with my build any more. Fingers crossed for an up-to-date Git release soon. Thanks for looking into this again. FWIW, the CVS on sourceare.org/cygwin.com is cvs-1.11.23-16.el6.x86_64. I've used it to import Cygwin's CVS into git so I know that it is possible. There is a limitation on cvsps though. As I understand it newer versions don't work with git. cvsimport also only works with cvsps v2 but that shouldn't be a problem since that's what we've got in Cygwin. cgf
Re: [ATTN maintainer] mined
On Fri, Jul 18, 2014 at 10:36:21AM +0200, Corinna Vinschen wrote: On Jul 18 06:39, Achim Gratz wrote: The mined directory for both architectures contain temporary files that apparently sftp has left there (they have the suffix SftpXFR.PID I think). These should be removed, but maybe the transfer script that moves the files from the upload area could be extended to ignore or delete such files so they never get distributed to the mirrors. I removed them on sourceware. If this happens again, please leave it for me to investigate. There is no reason why SftpXFR.PID files should be showing up in release directories. cgf
Re: Some programs (vi, ssh) crash when screen buffer height is big
On Fri, Jul 18, 2014 at 12:59:10PM -0400, sous lesquels wrote: Any suggestions? Or is this not as common use case as I think it is? Craft your reply with the appropriate In-Reply-To header tag and it will maintain threading. There is no automated way to do that if you are using the digest. Digests are intended for casual perusal of the list, not for active communication. -- 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
Re: Link count wierdness
On Fri, Jul 18, 2014 at 06:30:05AM +0200, Achim Gratz wrote: Christopher Faylor writes: git isn't ready yet unfortunately. Can't you just download a recent snapshot? That should be good enough. I can download and install snapshots just fine. I'm running snapshots for quite some time already so there'd be nothing new on that front. I'm talking about the source code for the snapshot. cgf -- 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
Re: Link count wierdness
On Thu, Jul 17, 2014 at 09:43:40PM +0200, Achim Gratz wrote: Corinna Vinschen writes: Netapp inode numbers are not reliable and thus the number of links isn't either. There's a check in Cygwin which is the result of the early Cygwin 1.7 development. It does not report the number of hardlinks and it fakes the inode numbers on netapp filesystems. Ah OK, that explains the wierd output from fstat. Is there a windows program to query that information, perhaps? The file system returns STATUS_INVALID_PARAMETER when calling NtQueryVolumeInformationFile(FileFsFullSizeInformation) for some reason. If you're set up to build your own Cygwin DLL, we could perform two or three really quick tests to find out if there's a way to workaround this issue in Cygwin. I am not yet but might be interested, is there a description somewhere of what that takes? I would need to use Git (is it ready yet?) since CVS gets blocked by the firewall and the various scrapers using CVSweb don't really work that well. git isn't ready yet unfortunately. Can't you just download a recent snapshot? That should be good enough. FWIW, CVS is blocked at my work (ironically, it's NetApp) too but I use a ssh tunnel to work around that. cgf -- 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
Re: pipe handling errors
On Wed, Jul 16, 2014 at 12:44:25PM +, Nellis, Kenneth wrote: From: Christopher Faylor On Tue, Jul 15, 2014 at 06:05:27PM -0400, Christopher Faylor wrote: Yes, I saw that, but I can't duplicate the problem with that command sequence. I took a stab at another change which may ameliorate the problem. Please try the latest snapshot. Indeed, with this snapshot I was not able to reproduce the problem. Thank you! Cygwin64 uname -srvmo CYGWIN_NT-6.1 1.7.31s(0.272/5/3) 20140716 11:15:29 x86_64 Cygwin Good to hear. Thanks for confirming. For the curious, I increased the size of the signal pipe buffer. I should have done that when I made signal pipes nowait to work around problems with gdb a couple of releases ago. I also made the signal sender retry if WriteFile returns success but the number of bytes sent was not what was requested (since these are message-style pipes the size should always be either zero or correct). Increasing the size of the buffer should have been enough to fix the problem but, when possible, I like to use two forms of protection when I fix a bug. -- 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
Re: Some programs (vi, ssh) crash when screen buffer height is big
On Wed, Jul 16, 2014 at 04:29:54PM -0400, sous lesquels wrote: A few more things to add: - This crashes under the regular Windows console, i.e. run cmd.exe, then bash, then follow the above You've discovered that Cygwin has limits. You can't run it with console windows that are too big. Sorry. cgf -- 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
Re: pipe handling errors
On Tue, Jul 15, 2014 at 07:17:48PM +, Nellis, Kenneth wrote: From: Nellis, Kenneth snip Well, I'm getting different results with the latest snapshot. Instead of getting the error message, I'm getting a hang for maybe a minute before it continues. I used the following command to encourage a failure: clear; for f in $(find */Debug -name '*Subsystem'); do echo === $f ===; strings $f | grep '\.cpp$' | sort | uniq -c | sort -n; done snip Thought it might be useful to add that I can fairly easily get the same minute-long hang with a simpler command: Cygwin64 strings *Subsystem | wc -l What's your cwd when you run this command? cgf -- 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
Re: pipe handling errors
On Tue, Jul 15, 2014 at 08:40:32PM +, Nellis, Kenneth wrote: From: Christopher Faylor On Tue, Jul 15, 2014 at 07:17:48PM +, Nellis, Kenneth wrote: From: Nellis, Kenneth snip Well, I'm getting different results with the latest snapshot. Instead of getting the error message, I'm getting a hang for maybe a minute before it continues. I used the following command to encourage a failure: clear; for f in $(find */Debug -name '*Subsystem'); do echo === $f ===; strings $f | grep '\.cpp$' | sort | uniq -c | sort -n; done snip Thought it might be useful to add that I can fairly easily get the same minute-long hang with a simpler command: Cygwin64 strings *Subsystem | wc -l What's your cwd when you run this command? Well, it *was* on a network drive, but that appears to be irrelevant: Cygwin64 date; seq 1 | wc -l; date Tue Jul 15 16:31:52 EDT 2014 1 Tue Jul 15 16:32:52 EDT 2014 Cygwin64 pwd /home/knellis Cygwin64 cygpath -w $PWD C:\cygwin\home\knellis Cygwin64 uname -srvmo CYGWIN_NT-6.1 1.7.31s(0.273/5/3) 20140715 15:34:37 x86_64 Cygwin Cygwin64 Yes, I saw that, but I can't duplicate the problem with that command sequence. cgf -- 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
Re: pipe handling errors
On Tue, Jul 15, 2014 at 06:05:27PM -0400, Christopher Faylor wrote: Yes, I saw that, but I can't duplicate the problem with that command sequence. I took a stab at another change which may ameliorate the problem. Please try the latest snapshot. cgf -- 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
Re: pngquant md5 mismatch?
On Mon, Jul 14, 2014 at 06:33:14PM +1000, Luke Kendall wrote: On 14/07/14 12:15, Christopher Faylor wrote: On Mon, Jul 14, 2014 at 11:05:48AM +1000, Luke Kendall wrote: For a few days now, mirrors.kernel.org has had a mismatch in the md5sum for the component pngquant-2.0.20130820+git1e28372-1-src.tar.bz2 in the pngquant package in the x86_64 architecture: $ grep pngquant-2.0.20130820+git1e28372-1-src.tar.bz [path-omitted]/cygwin-nightly/x86_64/setup.ini source: x86_64/release/pngquant/pngquant-2.0.20130820+git1e28372-1-src.tar.bz2 205502 ddf6b09472bb55ca46ab90f1f965572c $ md5sum [path-omitted]/cygwin-nightly/x86_64/release/pngquant/pngquant-2.0.20130820+git1e28372-1-src.tar.bz2 2c12df64c780640f38c7e4f78ee9 [path-omitted]/cygwin-nightly/x86_64/release/pngquant/pngquant-2.0.20130820+git1e28372-1-src.tar.bz2 I just downloaded the file manually and don't see any problem. The md5sum is correct. You're right. We seem to have an interesting problem at our end, for that single file. (We have the x86 component duplicated in the x86_64 for that single file only: size, date, data.) In case it isn't obvious, your nonstandard use of Cygwin mirrors is not something that should be debugged in this mailing list. If you have problems running setup*.exe then those will need to be fixed. Otherwise, please don't send problem reports like this here unless you can confirm that they actually affect people who are attempting to install Cygwin in the standard way. -- 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
[ANNOUNCEMENT] Updated: flex-2.5.39-1
I've made a new version of flex available for downloading. This updates the package to the latest version available from sourceforge. This update corrects the missing m4 dependency in the 64-bit version of flex. Thanks to Đ Đ¾Đ¼Đ°Đ½ Đ”Đ¾Đ½Ñ‡ĐµĐ½ĐºĐ¾ for the heads up about that. The flex program generates scanners. Scanners are programs which can recognize lexical patterns in text. Flex takes pairs of regular expressions and C code as input and generates a C source file as output. The output file is compiled and linked with a library to produce an executable. The executable searches through its input for occurrences of the regular expressions. When a match is found, it executes the corresponding C code. Flex was designed to work with both Yacc and Bison, and is used by many programs as part of their build process. Flex is available in tne Devel category. Below are the NEWS entries since the last release of flex. See the file COPYING for copying conditions. * flex version 2.5.39 ** no user visible changes in this release * version 2.5.38 released 2014-02-14 ** internationalization *** add sr translation from the translation project *** update da, es, ko, nl, pt_BR, ro, ru, sv, tr, vi, zh_CN translations from the translation project *** rename zh_tw to its proper zh_TW name * version 2.5.37 released 2012-08-03 ** Import flex into git. See git://flex.git.sourceforge.net/gitroot/flex/flex. ** Fix make install target to not fail when the flex++ program is already installed ** New translations from the translation project: de, fi, pl, vi * version 2.5.36 released 2012-07-20 ** various portability fixes that quiet compiler warnings on 64-bit hosts ** various manual fixes, including correcting the name of a %option and updating some simple examples to use ANSI C syntax ** various bug fixes that prevent certain error conditions from persisting when they should not persist ** improvements to the test suite so it behaves better when linking compiled files ** new translations from the translation project: ca, da, es, fi, fr, ga, ko, pt_br, ro, ru, sv, tr, zh_cn ** the flex distribution is now built with automake 1.10.1 and automake 2.61 -- 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
Re: pngquant md5 mismatch?
On Mon, Jul 14, 2014 at 11:05:48AM +1000, Luke Kendall wrote: For a few days now, mirrors.kernel.org has had a mismatch in the md5sum for the component pngquant-2.0.20130820+git1e28372-1-src.tar.bz2 in the pngquant package in the x86_64 architecture: $ grep pngquant-2.0.20130820+git1e28372-1-src.tar.bz [path-omitted]/cygwin-nightly/x86_64/setup.ini source: x86_64/release/pngquant/pngquant-2.0.20130820+git1e28372-1-src.tar.bz2 205502 ddf6b09472bb55ca46ab90f1f965572c $ md5sum [path-omitted]/cygwin-nightly/x86_64/release/pngquant/pngquant-2.0.20130820+git1e28372-1-src.tar.bz2 2c12df64c780640f38c7e4f78ee9 [path-omitted]/cygwin-nightly/x86_64/release/pngquant/pngquant-2.0.20130820+git1e28372-1-src.tar.bz2 I just downloaded the file manually and don't see any problem. The md5sum is correct. -- 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
Updated: flex-2.5.39-1
I've made a new version of flex available for downloading. This updates the package to the latest version available from sourceforge. This update corrects the missing m4 dependency in the 64-bit version of flex. Thanks to Đ Đ¾Đ¼Đ°Đ½ Đ”Đ¾Đ½Ñ‡ĐµĐ½ĐºĐ¾ for the heads up about that. The flex program generates scanners. Scanners are programs which can recognize lexical patterns in text. Flex takes pairs of regular expressions and C code as input and generates a C source file as output. The output file is compiled and linked with a library to produce an executable. The executable searches through its input for occurrences of the regular expressions. When a match is found, it executes the corresponding C code. Flex was designed to work with both Yacc and Bison, and is used by many programs as part of their build process. Flex is available in tne Devel category. Below are the NEWS entries since the last release of flex. See the file COPYING for copying conditions. * flex version 2.5.39 ** no user visible changes in this release * version 2.5.38 released 2014-02-14 ** internationalization *** add sr translation from the translation project *** update da, es, ko, nl, pt_BR, ro, ru, sv, tr, vi, zh_CN translations from the translation project *** rename zh_tw to its proper zh_TW name * version 2.5.37 released 2012-08-03 ** Import flex into git. See git://flex.git.sourceforge.net/gitroot/flex/flex. ** Fix make install target to not fail when the flex++ program is already installed ** New translations from the translation project: de, fi, pl, vi * version 2.5.36 released 2012-07-20 ** various portability fixes that quiet compiler warnings on 64-bit hosts ** various manual fixes, including correcting the name of a %option and updating some simple examples to use ANSI C syntax ** various bug fixes that prevent certain error conditions from persisting when they should not persist ** improvements to the test suite so it behaves better when linking compiled files ** new translations from the translation project: ca, da, es, fi, fr, ga, ko, pt_br, ro, ru, sv, tr, zh_cn ** the flex distribution is now built with automake 1.10.1 and automake 2.61
Re: Using fork() and pthread() OR how to link against cygwin?
On Fri, Jul 11, 2014 at 10:27:00AM -0500, Ismael FarfĂ¡n wrote: Hello list I've been searching allover the internet for fork gcc cygwin linker and stuff like that without much look :( In my test I use pthreads, fork, waitpid, random and other POSIX stuff, so the linker returns LNK2019 unresolved external symbol... That's not a GNU linker error message. You need to build Cygwin programs with Cygwin tools. What do I have to pass the compiler to get those functions? We use the ictl (intel) compiler, but gcc hasn't worked either. C library functions are in the in libc.a (aka libcygwin.a) but you need to be building a cygwin program using Cygwin's gcc for things to work properly. You can't just link in a library which contains fork into a Windows program. That won't work. cgf -- 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
Re: Emacs-w32... Still Crashing
On Tue, Jul 08, 2014 at 09:55:55AM -0400, Ken Brown wrote: On 7/7/2014 3:12 PM, Zdzislaw Meglicki wrote: The current version of Emacs that I have is emacs 24.3.91-1OK emacs debuginfo 24.3.91-1OK emacs-el24.3.91-1OK emacs-w32 24.3.91-1OK emacs-X11 24.3.91-1OK Cygwin is Cygwin DLL version info: DLL version: 1.7.30 DLL epoch: 19 DLL old termios: 5 DLL malloc env: 28 Cygwin conv: 181 API major: 0 API minor: 272 Shared data: 5 DLL identifier: cygwin1 Mount registry: 3 Cygwin registry name: Cygwin Program options name: Program Options Installations name: Installations Cygdrive default prefix: Build date: Shared id: cygwin1S5 Windows is Windows 8.1 Pro on AMD A8-5500 APU, 3.20 GHz, 64-bit OS, x64 CPU These days, Emacs no longer crashes as often as it used to. That's good to hear. So, there's been nothing to report until now. Emacs-w32 hanged and produced the do you want to enter debugger window, with the following backtrace produced by gdb: Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread 4532.0xa100] 0x7ff974f39e3b in KERNELBASE!DebugBreak () from /cygdrive/c/WINDOWS/system32/KERNELBASE.dll (gdb) bt #0 0x7ff974f39e3b in KERNELBASE!DebugBreak () from /cygdrive/c/WINDOWS/system32/KERNELBASE.dll #1 0x00010061a7a4 in emacs_abort () at /usr/src/debug/emacs-24.3.91-1/src/w32fns.c:8474 #2 0x00010043b702 in check_message_stack () at /usr/src/debug/emacs-24.3.91-1/src/xdisp.c:10993 #3 0x0001004fd763 in shut_down_emacs (sig=0, stuff=4305643570) at /usr/src/debug/emacs-24.3.91-1/src/emacs.c:2042 #4 0x0001004fd591 in Fkill_emacs (arg=60) at /usr/src/debug/emacs-24.3.91-1/src/emacs.c:1952 #5 0x0001004fb159 in terminate_due_to_signal (sig=15, backtrace_limit=40) at /usr/src/debug/emacs-24.3.91-1/src/emacs.c:360 #6 0x000100520429 in handle_fatal_signal (sig=15) at /usr/src/debug/emacs-24.3.91-1/src/sysdep.c:1630 #7 0x00010052035d in deliver_process_signal (sig=15, handler=0x100520411 ) at /usr/src/debug/emacs-24.3.91-1/src/sysdep.c:1570 #8 0x000100520444 in deliver_fatal_signal (sig=15) at /usr/src/debug/emacs-24.3.91-1/src/sysdep.c:1636 #9 0x000180070c8a in _cygtls::call_signal_handler (this=0x43ce00) at /usr/src/debug/cygwin-1.7.30-1/winsup/cygwin/exceptions.cc:1463 #10 0x000180111db8 in sigdelayed () from /usr/bin/cygwin1.dll #11 0x000100a2e832 in bss_sbrk_buffer () #12 0x in ?? () Thanks. All I can see from this is that a SIGTERM was generated, causing emacs to abort, but maybe someone else can see more. Grasping at straws, as usual, I wonder if these mysterious crashes could be related to a bug that Corinna just fixed: https://cygwin.com/ml/cygwin-cvs/2014-q3/msg4.html Corinna, is this plausible? If so, maybe Gustav should try the next snapshot of the Cygwin DLL. (The current one doesn't seem to have this fix in it.) Actually, I was scratching my head over that change and wondering what it was supposed to solve. cgf -- 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
Re: Emacs-w32... Still Crashing
On Tue, Jul 08, 2014 at 11:36:07AM -0500, Yaakov Selkowitz wrote: On 2014-07-08 10:02, Christopher Faylor wrote: On Tue, Jul 08, 2014 at 09:55:55AM -0400, Ken Brown wrote: Grasping at straws, as usual, I wonder if these mysterious crashes could be related to a bug that Corinna just fixed: https://cygwin.com/ml/cygwin-cvs/2014-q3/msg4.html Corinna, is this plausible? If so, maybe Gustav should try the next snapshot of the Cygwin DLL. (The current one doesn't seem to have this fix in it.) Actually, I was scratching my head over that change and wondering what it was supposed to solve. We believe that this was the cause of e.g. mandb aborting on x86_64 without manually enlarging the stack commit size: We? Isn't that testable by setting the stack size down and putting a printf in cygwin somewhere? In any event, the comment in my code which is supposed to explain why the tag is commented out is lacking details. If this patch is a joint effort then please add more details to the change that you made to my code. cgf -- 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
Re: cygport upload command?
On Mon, Jul 07, 2014 at 09:14:29PM -0400, Andrew Schulman wrote:
Using cygport, I think that packaging has become quite easy now. At least,
once the cygport script is built and working, updating a package to a new
release is as easy as updating the version number in the cygport script,
then running 'cygport ... download all'.
Except for one thing: the upload step. Maintainers still have to go
through the procedure at
https://sourceware.org/cygwin-apps/package-upload.html. Although it's
easier than the old manual upload process, it's still a little tedious and
error-prone.
Yaakov, would you consider adding an 'upload' command to cygport, that
would handle the uploading details? That would take away the last bit of
manual work in a routine package update.
If you don't have the time or interest to add an upload command yourself,
would you consider a patch? I've spent some time looking through cygport
code, and I might have time to give it a try, or maybe someone else would.
FWIW, this is the script that I use. Obviously the path to the upload
directory would have to be changed.
cgf
#!/usr/bin/perl
use strict;
use Getopt::Long;
my $arch = 'all';
GetOptions('a|arch:s'=\$arch);
use constant {
FTP = '/usr/bin/lftp'
};
my @arch = ();
if ($arch eq 'all') {
@arch = ('x86', 'x86_64');
} else {
@arch = $arch;
}
my $exit = 0;
for $arch (@arch) {
# ftp -c 'connect sftp://cygwin:@cygwin.com/; cd x86/release; mirror -eRN2
mutt; put /dev/null -o !ready'
chdir /netrel/uploads/$arch or die $0: couldn't cd to
/netrel/uploads/$arch - $!\n;
for my $p (@ARGV) {
print Uploading $p($arch)...\n;
my $res = system FTP, '-c', connect sftp://cygwin:\@cygwin.com/; cd
$arch/release; mirror -eR $p; put /dev/null -o !ready;
$exit ||= $res;
if (!$res) {
print done\n;
} else {
warn $0: $p upload failed\n if $res;
}
}
}
exit $exit;
Re: SSH key for upload access
On Fri, Jul 04, 2014 at 07:58:20AM +1000, Mark Hessling wrote: Name: Mark Hessling Package: regina-rexx BEGIN SSH2 PUBLIC KEY Comment: 2048-bit RSA, converted by mark@Windows7-64bit from OpenSSH B3NzaC1yc2EDAQABAAABAQCns1wj8gQNs/lmzMaqhPAyFAcCLFIm1Cqfkf7o5E yGAoMAVEMTnK3A1M0s1iGUhuX5k2r3EGPdLfsocfTRyw0+Ok5aj64sZVJc1/kaKkXw866M KTOhxlGlbilepL2y7I0BrzUcMlcA+hGjyo//5019aOBFrlV9NoglADl4GJc9RWNMe/GkLe W1kgOLZCufB8QPwsvE5cTcD4qov5A0P46HC3d1VHEA3cQzJCsNuOUdHIlXeDv/hUVWhRVs GSaqLoxpC3QRCSn8MVRQ44k56kW6gcSk2ro5YcEgtm5xMGDgbK1akTvC0GW4dnUNA5ElOi M6ZRWei2SEpT7l8KkYBFf7 END SSH2 PUBLIC KEY Activated. cgf
Re: [ITP] regina-rexx-3.8.2-1
On Thu, Jul 03, 2014 at 12:49:52PM +0200, Corinna Vinschen wrote: I've added you as regina-rexx maintainer. Can you please send your ssh key per https://sourceware.org/cygwin-apps/package-upload.html Sigh. You have to first add... Oh! Wait. Nevermind. *Blush* cgf
Gold star Re: [ANNOUNCEMENT] Updated: rcs-5.9.2
On Thu, Jul 03, 2014 at 07:59:42PM +0200, Achim Gratz wrote: This release brings RCS to version 5.9.2 for both architectures and includes a patch for the RCS work file corruption problem that has been discussed on the Cygwin mailing list and reported to rcs-bugs: Could we get a gold star for Achim here? He's fixed a long-standing problem in RCS and taken over maintainership. Thanks Achim. -- 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
Re: Feature request - option to save username and password for proxy in setup.exe
On Wed, Jul 02, 2014 at 07:03:31AM +0530, Siddhant Saraf wrote: Hello, I like that setup.exe remembers the HTTP proxy host name and port for the subsequent runs of setup.exe. If the proxy requires authentication, it prompts for username and pasword. Can it include an option to save the username and password too ? Maybe it can have a checkbox which says Remember username and password. This shouldn't be too hard to implement if someone wants to take a stab at submitting a patch. You can save these values in the setup.rc file. You can check out setup sources via CVS: https://sourceware.org/cygwin-apps/setup.html cgf -- 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
Re: can't share fifo between 32-bit and 64-bit Cygwins
On Mon, Jun 30, 2014 at 10:08:24PM +0200, Marco Atzeri wrote: On 30/06/2014 20:04, Nellis, Kenneth wrote: Just thought I'd share an observation I found interesting. Not a problem for me, so not asking for any particular response. If I create a named pipe (mkfifo), as long as I write to and read from using either 32-bit Cygwin or 64-bit Cygwin, all works fine, but if I write with either one and read with the other, both processes hang. It doesn't seem to matter whether the fifo was created under 32-bit or 64-bit, the problem (if I may be so bold as to call it that) seems only with mixing 32-/64-bit versions doing I/O to/from it. FWIW, using 32-bit version 1.7.29-2 and 64-bit version 1.7.30-1. why do you expect such things to work ? You have two separate simulation layers independent from each other. Nothing is in place to pass the data from the 32 bit layer to the 64 layer. Right. Fifos, signals, ptys - all of them are distinct entities that won't work between 32 bit and 64 bit or even between different Cygwin installations on the same system. cgf -- 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
Re: tmux-1.9a2 ctrl+b not working
On Thu, Jun 26, 2014 at 01:56:18PM -0700, DJ Sylvester wrote: I searched Google. I looked at sourceforge tickets http://sourceforge.net/p/tmux/tickets/ I've read this Cygwin tmux announcement: https://cygwin.com/ml/cygwin-apps/2014-06/msg00018.html I've reinstalled tmux with cygwin-x86 installer. I've had no luck. ctrl+b command is not working for me. I'm running a default mintty as installed by cygwin-x86 on Win-7 with a few aliases defined, nothing else. My.tmux.conf file is empty. To reproduce: 1. start tmux 2. ctrl+b % (outputs 5u) 3. ctrl+b (no outputs, does nothing) 4. ctrl+b c (no outputs, does nothing) No commands are working. Not sure what to try next. Sorry but this isn't the right mailing list for reporting problems. Please use the cygwin mailing list for problem reports, just like it says at https://cygwin.com/lists.html#available-lists .
Re: developing 32-bit and 64-bit in a shared environment
On Wed, Jun 25, 2014 at 01:04:24PM +, Nellis, Kenneth wrote: I have happily been using 32-bit Cygwin for years, developing shell/perl scripts and C/C++ software. Some of the users that I support have upgraded to 64-bit Cygwin, and so my 32-bit C/C++ binaries no longer work for them. That has forced me to adopt 64-bit Cygwin, which I've installed on the same machine as my 32-bit Cygwin. I need to maintain both environments in parallel. Now, I want to share my Cygwin $HOME directory between the two environments. I already keep my binaries in $HOME/bin/$(arch) and $HOME/lib/$(arch), so they are covered. And, of course /usr/bin has to continue to point to the separate Cygwin environments. I didn't see what I was looking for in the FAQ or User Guide, so am looking for advice from the list. I think you're looking for this: https://cygwin.com/cygwin-ug-net/using.html#using-pathnames i.e., use /etc/fstab to mount your home directory to the same place in both environments. cgf -- 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
[ANNOUNCEMENT] Updated: binutils-2.24.51-4 (x86/x86_64)
I've made a new version of binutils available for installation. This is a refresh against the official git repository. The binutils package contains the GNU assembler, linker and binary utilities. It is available in the Devel category under Cygwin's setup. -- 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
Re: [ANNOUNCEMENT] Updated: rsync 3.0.9-1 -- fast, versatile file synchronizing tool
On Mon, Jun 23, 2014 at 02:55:02PM +0200, Corinna Vinschen wrote: On Jun 23 12:35, Achim Gratz wrote: Since the new release doesn't provide a rsync-debuginfo package, there should be setup.hint file that makes the old debuginfo package the previous version. I guess Jari just forgot to upload the debuginfo packages. They are auto-generated by cygport anyway. Jari? I don't believe that Jari uses cygport. cgf -- 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
Re: [ANNOUNCEMENT] Updated: zip-3.0-2
On Mon, Jun 23, 2014 at 06:29:11PM +0200, Achim Gratz wrote: Corinna Vinschen writes: I fixed this on cygwin.com by adding prev and curr entries. Confirmed, thanks. Isn't the real question why the numbering went backwards? It sounds like there is a packaging error here and this should have been zip-3.0-12 rather than zip-3.0-2. cgf -- 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
Re: Too many mailing lists(passing the buck)
On Sun, Jun 22, 2014 at 02:21:49PM -0700, Linda Walsh wrote: Adam Dinwoodie wrote: On Fri, Jun 20, 2014 at 03:07:37PM -0600, Warren Young wrote: Every time someone says That's not on topic here, go elsewhere, it can easily be read as Go away. The Cygwin project should only be pushing away toxic people, and multiple mailing lists do not have that happy side effect. I've never seen a reply saying that's not on topic here, go away that could be read as you describe. You didn't even bother to check google? i settled on looking at bash: bash cygwin off-topic -stackoverflow But have seen similar for X11 related. on the first page: (all talking about the topic being wrong for the list involved). https://cygwin.com/ml/cygwin/2003-12/msg00252.html https://cygwin.com/ml/cygwin/2001-03/msg00691.html https://cygwin.com/ml/cygwin/2008-11/msg00423.html https://cygwin.com/ml/cygwin/2013-02/msg00343.html vs. the opposite problem where a cygwin devel yanked my prob from a cp-bug-report and closed it: bug was related to a case-bug using cp -a and being told it was a cygwin bug unless I could recreate it on linux (even though the bad code was in 'cp'.) (had to do with ignoring case, and creating it with a case ignoring FS on linux would have been too much of a pain (like XFS has such an option) . project owners constantly like to pass the buck in hopes the user will give up...usually project owners win because reporting bugs is too much trouble. But, then, I know of cygwin devs who feed orphans, rescues kittens, and work to prevent global warming. So, as long as we're making unsubtantiated allegations, it all works out in the end. cgf -- 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
Re: Too many mailing lists(passing the buck)
On Sun, Jun 22, 2014 at 09:10:06PM -0400, Larry Hall (Cygwin) wrote: On 06/22/2014 05:38 PM, Christopher Faylor wrote: But, then, I know of cygwin devs who feed orphans, rescues kittens, and work to prevent global warming. So, as long as we're making unsubtantiated allegations, it all works out in the end. Would it be wrong of me to point out that we may have gone off-topic with all this talk of passing the buck and feeding orphans? Oh, the irony of it all! OK, sorry. I just couldn't resist. ;-) It's a good point though. I think I might have to set up a cygwin-orphans-etc mailing list. cgf -- 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
Re: Package file lists archive
On Tue, Jun 17, 2014 at 11:29:53PM -0500, Steven Penny wrote: On Tue, Jun 17, 2014 at 9:29 AM, Christopher Faylor wrote: On Mon, Jun 09, 2014 at 11:17:11AM -0500, Steven Penny wrote: Of course because of Cygwin flawless website... If you want to experimentally figure out how many warnings you get, please go right ahead and continue with this style of communication. Really, I can do without veiled threats. If you are going to ban me or whatever, go ahead and do it. I have brought some constructive criticisms of this project with the hope of starting a discussion around fixing/improving certain issues. Instead I am met with brick wall attitude and threats of being pushed off the mailing list. Your idea of constructive is apparently flawed. The comment that you cut (and I just put back) illustrates what I was talking about, as does your suggestion that I should contact Debian maintainers because I disagreed with the idea of maintaining a package file list. Your truculent insistence that I should knight you as the coreutils/bash maintainer is another example. My suggestion has merit: Debian is no niche operating system and apt-get is no niche package manager. You can make any suggestions you want. Just avoid the snide asides. cgf -- 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
Re: Package file lists archive
On Wed, Jun 18, 2014 at 01:53:14AM -0500, Steven Penny wrote: On Wed, Jun 18, 2014 at 1:18 AM, Christopher Faylor wrote: Your idea of constructive is apparently flawed. This is an interesting comment, taking in that your response ignores the original question and focuses on off topic quibbling. I will pose your viewpoint and my question again I was actually staying on-topic with what I wanted to address: namely the thin ice that you are walking with your posting style. And, frankly, I think it's a bad idea to keep a monolithic list of packages available for people to download anyway. Do you have an explanation for this opinion, or citations as to why this is a bad idea, taking into account that major Linux distros are already using this very method? Frankly, I don't have to justify my opinion. I understand how the package generation would have to work and don't see a major benefit to introducing a package list file given the amount of work and the fact that I would have to do the work. I also don't want to spend my time debating with you about why it is or isn't a good idea. cgf -- 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
Re: Package file lists archive
On Wed, Jun 18, 2014 at 09:24:13AM -0500, Steven Penny wrote: On Wed, Jun 18, 2014 at 7:28 AM, Larry Hall (Cygwin) wrote: If this was the question you wanted to ask originally, this is all you needed to add to the thread. Hey Larry, thanks for your comments. However, did you have anything constructive to add, like an answer to the question? Although we are friends, there is no reason to expect Larry to be able to explain my opinions. Please move on. This isn't going to happen. Or take it to cygwin-talk. cgf -- 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
gold star (was Re: [ANNOUNCEMENT] New package: man-db-2.6.7-1)
On Wed, Jun 18, 2014 at 09:41:19PM +0200, waterlan wrote: Chris J. Breisch schreef op 2014-06-18 03:01: Version 2.6.7-1 of man-db has been uploaded. DESCRIPTION === man-db is an implementation of the standard Unix documentation system accessed using the man command. It uses a Berkeley DB database in place of the traditional flat-text whatis databases. HOMEPAGE http://www.nongnu.org/man-db/ Thanks Chris. The international man pages are displayed correctly now on Cygwin. Sounds gold star worthy to me. Andrew, could you make it so when you have a chance? cgf -- 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
Re: No glibc in cygwin
On Wed, Jun 18, 2014 at 11:03:52PM +, Lucero, Aldo wrote: I am trying to port some Fortran/C code from Linux to Windows using Cygwin (CYGWIN_NT-6.1 elp-w7wks-40 1.7.30(0.272/5/3) 2014-05-23 10:36 i686 Cygwin) The main program spawns several processes using fork() and one of those processes will create another process using clone(). I have read under the FAQ that glibc is not part of Cygwin and that using fork in Cygwin is not stable. fork() in Cygwin has to be pretty stable since it is fundamental to a UNIX/Linux system. Cygwin doesn't implement clone() however. It is theoretically possible to do so but it wouldn't be trivial. I have been able to compile my code in Cygwin, but when trying to link my libraries (static), it cannot find clone function (under C code). Do you guys have any recommendations as far as whether to continue trying to get my code to work under Cygwin or should I try to find some other Windows compiler(s)? I apologize if I am not being clear, but I am wondering if somebody else has had this issue and if they were able to resolve it. This isn't a compiler issue. You'd have to find something similar to Cygwin which implemented clone(). Or add the functionality yourself. cgf -- 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
Re: SSH key for upload access
On Tue, Jun 10, 2014 at 07:21:30PM +0200, Thomas Wolff wrote: Name: Thomas Wolff Package: mined BEGIN SSH2 PUBLIC KEY Comment: 2048-bit RSA, converted from OpenSSH by root@MyBookLive B3NzaC1yc2EBIwAAAQEAwMSnVCjNhyiGNhBC/+uPheB4BgG+n7RVmVMiBUJkIy 19fDeLc+0bWgzKLEXl00e0KytGgz6gS3sbDYfv8Ukh9eAnQ9iev31fZmb2UpmXtJCpQHrK tT3kT3FME+sDX3zYCnpXyOGUP0v0DwUSbRdsMyzH3YKw8XJ60b2gi5PX1wTENR0L4fnXUr +3Wya4jXUR5d5Az7/Yn9HrBc68qogHn+TwBFZUhXMtlcThKoRBA7160Td7sUeTc1FoqvlD saneqqnZCgX0qhWZp9V+eNHMnMkNoSwhdDtM+7IRI0doTI7BlzLbiZp1mZOUNWDtdaZwIn Jbtk5T/FDLw+VIQQWmcQ== END SSH2 PUBLIC KEY Activated.
Re: SSH key for upload access
On Fri, Jun 06, 2014 at 08:07:16PM -0400, Chris J. Breisch wrote: Name: Chris J. Breisch Package: man-db BEGIN SSH2 PUBLIC KEY Comment: 4096-bit RSA, converted by Chris@Chris-PC from OpenSSH B3NzaC1yc2EDAQABAAACAQCzGcbs64ShqbQOi1hpyrCVay5NAsV+DG+39LnIlv tiP07M8+92jo4UQUcXXLhXevoktmm6xPbzqote/TcNXUmjh7ZRCs5FW16X/++CqxKK3nMu lRrMoAVZ0+T8rNZ1FNFq11BsF5irJqtU3NetCOdo0ihCUCYxzjSWctolq98vLwIyb2VUnX BPPUH4Ez+1ZAyUIa7ppSMWDeny55sovGGqODbLrYbhhfiP5ubFwNqMr73BU8xN4W2tXkUl VBA8uIwdEMwsSzD1rfJ1BCLsgVc2Rh2CWSvcA4Ryj5ycD+Rn2r20ttbxK598JfYD5Lnw2H HYAZRmq16kmN1K6/WczBrcWAFIohlHVMIhr6LA7MSXXqPO7en/EGQ+XaIoAZdN3KjHFhxM FJGBRhmdrSSno9s9BsOKYABN1K08oLV0jOYzop/4dByVubkByaXJSzgyGD/ckISlndYkIz Nw1KkvP3Ta0iPiyxQpmHMtkVDEG8BDassr9MhH7WSgZcN1hKE9BmXgz36tepLP5jxKWlxb DsomiCokufHIJGJiuNiIuNwPDEoB8XeNCzKYEXnEFT03sGHrmjTc2236rM3lvkw+MfuGGo VmIhzcasQPlSdG64LZhOaX8pTHiGG5pHDK7NRtZZuFrhE5dFUV5LBiFFCP4lSXYMQ90O3k Me/IFsdBwJIqBQ== END SSH2 PUBLIC KEY Activated.
Re: Package file lists archive
On Thu, Jun 12, 2014 at 04:58:25PM -0500, Steven Penny wrote: On Mon, May 26, 2014 at 3:12 PM, Christopher Faylor wrote: And, frankly, I think it's a bad idea to keep a monolithic list of packages available for people to download anyway. I would counter that Debian and others who use apt-get already do this, Example http://http.debian.net/debian/dists/wheezy/main/Contents-amd64.gz This file maps each file available in the Debian GNU/Linux system to the package from which it originates. It includes packages from the DIST distribution for the ARCH architecture. You can use this list to determine which package contains a specific file, or whether or not a specific file is available. The list is updated weekly, each architecture on a different day. so maybe you could voice your opinion to them as well. FYI, trolling is obviously off-topic here. It's nice that you found a solution to your problem, however. cgf -- 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
Re: Package file lists archive
On Mon, Jun 09, 2014 at 11:17:11AM -0500, Steven Penny wrote: On Mon, Jun 9, 2014 at 10:17 AM, Warren Young wrote: Speaking of, is the source for package-grep.cgi available somewhere? I http://cygwin.com/cgi-bin/cvsweb.cgi/htdocs/cgi-bin2?cvsroot=cygwin Of course because of Cygwin flawless website, this is not indexed by Google and not even linked on Cygwin.com, so you are a left with Isla de Muerta. Ok Mr Penny. Here's warning 1 for you: Can the attitude. I'm sick of it. If you want to experimentally figure out how many warnings you get, please go right ahead and continue with this style of communication. cgf -- 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
Re: Website: Package listing not working
On Mon, Jun 09, 2014 at 07:19:04PM +0100, David Stacey wrote: On the cygwin.com website, none of my packages display their contents correctly, e.g.: https://cygwin.com/packages/x86/keepassx/keepassx-0.4.3-2 https://cygwin.com/packages/x86/libpoco-devel/libpoco-devel-1.4.6p3-1 https://cygwin.com/packages/x86/doxygen/doxygen-1.8.7-1 All I see is a long list of zeros. Other people's package listings are fine, e.g.: https://cygwin.com/packages/x86/libopenssl100/libopenssl100-1.0.1h-1 https://cygwin.com/packages/x86/texlive-collection-basic/texlive-collection-basic-20130529-1 Is this a website problem? Or have I managed to get something seriously wrong in building my packages? I'm using Firefox 29.0.1 under Fedora 20 64-bit, although looking at the source code it seems as though the browser is rendering the pages correctly. It's not a website problem. It is apparently a problem with the upset script which generates these listings. I'm investigating. cgf -- 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
Re: Website: Package listing not working + cygport query
On Tue, Jun 17, 2014 at 10:31:11AM -0400, Christopher Faylor wrote: On Mon, Jun 09, 2014 at 07:19:04PM +0100, David Stacey wrote: On the cygwin.com website, none of my packages display their contents correctly, e.g.: https://cygwin.com/packages/x86/keepassx/keepassx-0.4.3-2 https://cygwin.com/packages/x86/libpoco-devel/libpoco-devel-1.4.6p3-1 https://cygwin.com/packages/x86/doxygen/doxygen-1.8.7-1 All I see is a long list of zeros. Other people's package listings are fine, e.g.: https://cygwin.com/packages/x86/libopenssl100/libopenssl100-1.0.1h-1 https://cygwin.com/packages/x86/texlive-collection-basic/texlive-collection-basic-20130529-1 Is this a website problem? Or have I managed to get something seriously wrong in building my packages? I'm using Firefox 29.0.1 under Fedora 20 64-bit, although looking at the source code it seems as though the browser is rendering the pages correctly. It's not a website problem. It is apparently a problem with the upset script which generates these listings. I'm investigating. I'm surprised that I haven't seen this before: The name that you used to generate your packages was David Stacey/None. My parser wasn't expecting a name with a space and I didn't detect the fact that the parsing failed (#($ just realized that I forgot to fix that). So it was just outputting a '0' size, one per line. Yaakov, wouldn't it make sense not to just use 0/0 as user/group when generating packages with cygport by forcing --owner=0, --group=0 to the tar command? I'm not suggesting that this is the right way to fix this particular problem but I don't think it's a good idea to leak people's names and groups out onto the interwebs if we can help it. It will also make the packages slightly smaller. cgf -- 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
Re: Website: Package listing not working + cygport query
On Tue, Jun 17, 2014 at 11:32:00AM -0400, Christopher Faylor wrote: I'm surprised that I haven't seen this before: The name that you used to generate your packages was David Stacey/None. My parser wasn't expecting a name with a space and I didn't detect the fact that the parsing failed (#($ just realized that I forgot to fix that). So it was just outputting a '0' size, one per line. Just to be clear: This was 100% my problem. You should have been able to use any name you want in the tar file and my script should have been robust enough to handle it. cgf -- 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
Re: Website: Package listing not working + cygport query
On Wed, Jun 18, 2014 at 12:04:29AM -0500, Yaakov Selkowitz wrote: On 2014-06-17 10:32, Christopher Faylor wrote: I'm surprised that I haven't seen this before: The name that you used to generate your packages was David Stacey/None. My parser wasn't expecting a name with a space and I didn't detect the fact that the parsing failed (#($ just realized that I forgot to fix that). So it was just outputting a '0' size, one per line. Yaakov, wouldn't it make sense not to just use 0/0 as user/group when generating packages with cygport by forcing --owner=0, --group=0 to the tar command? I'm not suggesting that this is the right way to fix this particular problem but I don't think it's a good idea to leak people's names and groups out onto the interwebs if we can help it. It will also make the packages slightly smaller. That would undermine any legitimate specification of gid/uid. I would like to see how this is handled in the Linux distros first. I don't see how the random uid/gids of a user would ever be legitimate. Some released rpm packages do contain (incorrectly, imo) the uid/gid of the build system that created them but rpm does have a mechanism for specifying ownership. If it was really important that arbitrary ownership must be assigned for some package then it seems like that would be another cygport enhancement since there is no easy way for a package maintainer to force their uid to some other value. cgf -- 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
Re: Emacs-w32... still crashing
On Thu, Jun 05, 2014 at 03:05:43PM -0400, Ken Brown wrote: On 6/3/2014 6:00 PM, Zdzislaw Meglicki wrote: And... another crash. I didn't run it under gdb this time and it didn't dump anything either, but I got interesting new message I didn't see before: *** fatal error - WFSO failed waiting for timer thread, Win32 error 0 This message comes from the function timer_tracker::cancel in timer.cc in the Cygwin sources. I'm afraid I have no idea what the timer thread is or why WaitForSingleObject might fail waiting for it. cgf or Corinna (or anyone else), can you shed any light on what might cause this? Could it be BLODA, for instance? I really don't see how WaitForSingleObject can fail like this but I have demoted that fatal condition to a warning and added slightly more debugging output to it. The next snapshot will have that change. cgf -- 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
Re: Native links break zsh
On Wed, Jun 04, 2014 at 12:56:45PM +0400, Yuriy Chernyshov wrote: Hi! After adding export CYGWIN='winsymlinks: nativestrict' command to my .zshrc file I'm experiencing the problem with zsh HISTFILE. The message says: History locking file failed: No such file or directory. I don't know how this is related since HISTFILE isn't a link at all. This is not a bug reporting mailing list. You've already posted this topic to the cygwin list and you have had responses to your message. Please continue the discussion there. I'm unsubscribing you from cygwin-apps.
Re: Compiling cygwin1.dll
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 HAVE the whole toolchain. cgf -- 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
Re: Are there any SELinux tools available for Cygwin?
On Tue, Jun 03, 2014 at 01:20:26PM -0600, Warren Young wrote: One of the biggest mistakes people make when asking for help is specifying the solution in advance. Amen. cgf -- 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
s/Chuck Wilson/Former Maintainer/
I see that Yaakov just removed Chuck Wilson (ostensibly temporarily) as a maintainer. That makes me very sad. I sincerely hope that Chuck is just busy in real life. It is rather frustrating to be concerned about someone and have no way to know for sure that they are ok. cgf
Re: Regarding debug_printf in your code base.
On Sat, May 31, 2014 at 07:01:40PM +0530, Abhijit Bhattacharjee wrote: In your code base, I can see in lot of places there are calls to debug_printf, example How do I invoke/build cygwin so that debug_printf dumps debugging information to the console. By personally modifying the code to do something it wasn't designed to do. cgf -- 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
Re: Bash silently truncates the Command Line when called programatically via CreateProcess as MAXPATHLEN was reduced to 8192 from 16384
On Sat, May 31, 2014 at 06:58:59PM +0530, Abhijit Bhattacharjee wrote: Thank you everyone for your time and reply. I believe from your reply I am able to get the problem sorted out. I would also try to reply to each of your queries @Christopher Faylor Qs/Stmt: A Cygwin program which calls another Cygwin program does not have this problem so it isn't completely immaterial. Ans: I am not sure what you mean by Cygwin program. If you mean those that are in your repository, I cannot comment. Instead, if you mean, that's linked with cygwin1.dll, I believe, I have already shared with you sample programs that exhibits the truncation behavior. I should have been clearer. What I mean by Cygwin programs are programs linked with the Cygwin DLL, using only Linux/POSIX functions. If program A exec's program B using one of Cygwin's exec/spawn functions it will not suffer from command line truncation. But, if you choose to use Windows APIs then you are on your own. There is no guarantee that Cygwin functionality like process handling, signals, pipes, etc. will work reliably. Qs/Stmt: Possibly setting the CYGWIN environment variable to noglob might cause things to work as desired. Ans: I am yet to test this, but I trust your answer. I am yet to figure out as to how I can set the environment variables CYGWIN with multiple values i.e. I need to set it with nodosfilewarning and noglob. I was trying to read though your code environ.cc and seems to me I can simply separate it with a delimiter. Your documentation is silent about it. If you know it off hand, please let me know, that will reduce some effort for me to read and debug though your code :-) The documentation is most definitely not silent. https://cygwin.com/cygwin-ug-net/using-cygwinenv.html makes it very clear in the second sentence of the above section. cgf -- 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
Re: Update CoreUtils
On Sat, May 31, 2014 at 02:29:30AM -0700, PolarStorm wrote: Hello, [snip] Ok, there is no new information here. I'm declaring this off-topic for the cygwin list and asking people to send any follow-ups to the cygwin-talk. -- 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
Re: Are there any SELinux tools available for Cygwin?
On Sat, May 31, 2014 at 01:40:53AM -0700, PolarStorm wrote: Warren Young wrote There is an excellent tool for managing SELinux on remote machines, and it is packaged for Cygwin. It is called ssh. Perhaps you have a package to prevent idiots from answering here as well? Install it please. Please abstain from name-calling. cgf -- 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
Re: Update CoreUtils
On Thu, May 29, 2014 at 05:49:53PM -0500, Steven Penny wrote: On Thu, May 29, 2014 at 08:12:46PM -0500, Steven Penny wrote: On Thu, May 29, 2014 at 7:04 PM, Chris J. Breisch wrote: On Thu, May 29, 2014 at 12:11 PM, Christopher Faylor wrote: So the bottom line is that git's status is: missing a maintainer, hoping for someone to pick it up. You have short term memory? Do you? https://cygwin.com/ml/cygwin/2014-05/msg00284.html From the same thread. Amazing that you missed that. You are out of your element, mate https://cygwin.com/ml/cygwin/2014-05/msg00298.html Nope. You are confused. Eric indicated 1) that he wanted to give up git and 2) he did not want to give up bash or coreutils. David Conrad was talking about git. So, as I said, we are missing a git maintainer even though we did have someone trying to take on that responsibility. You should be aware of what happened with git and should be able to discern a template for how to go about adopting it. Chest thumping and rambling essays aren't going to magically make you a maintainer. If you are interested then, as I mentioned in the link that you quoted, you have to learn the rules for becoming a maintainer. You don't need me to touch your shoulders with a sword to make things happen. Oh, and just in case I get quoted in the future again, I'll make it clear again: I'm talking about git, not coreutils or bash. cgf -- 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
Re: It's back -- gcc: error: spawn: No such file or directory
On Fri, May 30, 2014 at 11:19:37AM -0500, David Friedman wrote: I just upgraded my gcc to 4.8.3 and tried a compilation, and got the error above. I see that there's been some previous discussion of this error, including whether gcc is started from /usr/bin or /bin; tried both, no difference. See below: $ echo $PATH /usr/local/bin: /usr/bin: /bin: /usr/X11R6/bin: /cygdrive/c/WINDOWS/system32: /cygdrive/c/WINDOWS: /cygdrive/c/WINDOWS/system32/wbem: /cygdrive/c/program files/intel/dmix: . . . Try removing /bin from your path entirely. cgf -- 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
Re: Update CoreUtils
On Thu, May 29, 2014 at 12:56:41PM -0400, David Conrad wrote: On Tue, May 13, 2014 at 11:04 AM, Christopher Faylor wrote: On Tue, May 13, 2014 at 09:59:03AM -0500, Steven Penny wrote: . . . Funny how you're saying We as if you are actually contributing anything other than criticism. I started a thread, at one point, to ask about a newer version of git. I offered to try to create a build, if it would help, even though while I have over a decade of experience in the software industry I have no experience as a Cygwin package maintainer. I also found that Steven Penny had offered, six months or a year before my thread, to build it. Adam Dinwoodie stepped up and offered to take over as maintainer. He got a build out in short order, but there was a glitch in either the cygwin dll or in openssl, I forget which, that caused long-running git clones to fail. Once that was fixed, everything seemed to be working except for something with git-cvs. I've never used git-cvs, and haven't used CVS since early 2009, so I didn't know how I could help with testing or resolving that issue. If I could have, I would have. I continued to use Adam's git build of 1.8.5.2 for the next couple of months, but it slowly started to bother me more and more that I was using a beta build. I didn't want to go back to git 1.7.9 because that version is well over two years old now (although, admittedly, I never had trouble with it). So I installed the native Windows git (msysgit) 1.9.2 from git-scm.org. It took a bit of configuring to get it to play nice with Cygwin. I need git because all my company's projects are in git (nearly; a few stragglers are still using svn). I wish there was a Cygwin build that was, say, a year old or less. (I still have one problem, that occasionally when it runs an external tool, it uses its msys bash which doesn't understand SHELLOPTS=igncr, which I need because of some stupid \r characters in the shell scripts of npm from nodejs.) I love Cygwin. I've been a happy user for years. Cygwin bash makes using Windows tolerable, which makes my life better. I deeply appreciate everything you all do, and I know that you're volunteers. I have no claim on your time, or your effort. If I have to build a few things myself, or use another version, I can do that. But it does look like some people have tried to help. I'm sorry I wasn't able to be of more help. There's no need for a reply to this. If you read this far, then thank you for your time, and thank you for all you do. The intent of this message isn't clear to me. You've just filled us all in on your experience trying to use git and noted that we need a git maintainer. I guess people who aren't aware of that are now aware. So the bottom line is that git's status is: missing a maintainer, hoping for someone to pick it up. Hopefully the subtext isn't that this is stalled because someone like Corinna or I didn't jump in to try to fix problems with git... cgf -- 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
Re: make install problem for emms (Permission denied)
On Fri, May 30, 2014 at 01:50:49AM +0400, Filipp Gunbin wrote: Also, it's strange that the install... command above works when run directly in shell, but fails when run from make. Which implies that you probably are not running /usr/bin/install. cgf -- 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
Re: Bash silently truncates the Command Line when called programatically via CreateProcess as MAXPATHLEN was reduced to 8192 from 16384
On Wed, May 28, 2014 at 05:41:19PM +0200, Houder wrote: As far as I can tell, it is not bash, but the Cygwin supervisor, that does the truncation. The code in Cygwin has already been repeatedly identified. Possibly setting the CYGWIN environment variable to noglob might cause things to work as desired. See: https://cygwin.com/cygwin-ug-net/using-cygwinenv.html Also remember that this environment variable has to be set before any Cygwin program is run, i.e., from the CMD prompt or by setting the environment variable globally via, e.g., Control Panel-System-Advanced system settings-Environment Variables cgf -- 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
[ANNOUNCEMENT] Updated: binutils-2.24.51-3 (x86/x86_64)
I've made a new version of binutils available for installation. This is a refresh against the official git repository. The binutils package contains the GNU assembler, linker and binary utilities. It is available in the Devel category under Cygwin's setup. -- 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
Updated: binutils-2.24.51-3 (x86/x86_64)
I've made a new version of binutils available for installation. This is a refresh against the official git repository. The binutils package contains the GNU assembler, linker and binary utilities. It is available in the Devel category under Cygwin's setup.
Re: Package file lists archive
On Mon, May 26, 2014 at 10:18:20PM -0500, Steven Penny wrote: On Mon, May 26, 2014 at 3:12 PM, Christopher Faylor wrote: And, frankly, I think it's a bad idea to keep a monolithic list of packages available for people to download anyway. Could you not just require each package includes a file list? This way you could get the information from any mirror. Not interested. This would ease the burden of the cygwin.com site, as it is the only site with that information currently It is surviving just fine. cgf -- 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
Re: Bash silently truncates the Command Line when called programatically via CreateProcess as MAXPATHLEN was reduced to 8192 from 16384
On Tue, May 27, 2014 at 06:49:43PM +0530, Abhijit Bhattacharjee wrote: Yes, MSVS is Microsoft Visual Studio. and I am using the make for Windows (http://gnuwin32.sourceforge.net/packages/make.htm). Please note, when I am saying the path is getting truncated, its the bash that is truncating it. Also, its immaterial how and what is getting called. With the latest Cygwin, any program that is compiled and linked with the CRT would exhibit this behavior. The truncation issue in the CRT is best demonstrated by the following Code couplets A Cygwin program which calls another Cygwin program does not have this problem so it isn't completely immaterial. Also Note, if you would like to review the code that is responsible for the truncation, I would suggest you to refer the function Not sure who you are talking to but, on the off chance that you are hoping to engage a Cygwin developer, we do know where the glob code lives. As I indicated, it originally comes from FreeBSD. Quoting myself: On Mon, May 26, 2014 at 04:08:57PM -0400, Christopher Faylor wrote: Since this isn't really an issue when Cygwin calls Cygwin programs it likely isn't really high on anyone's priority list. -- 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
Re: [PATCH] cygwin_rexec() returns pointer to deallocated memory
On Mon, May 26, 2014 at 04:27:10PM +0100, David Stacey wrote: On 26/05/14 14:36, Peter Rosin wrote: I believe the comment refers to if static is the right answer to the problem. Is there a need to handle concurrent calls? I can't really comment on that. As the code stands, neither of the two functions that we are discussing are reentrant. As long as the author and the user(s) of the routines are both aware of that then it isn't a problem. I was just trying to fix a coding error that was picked up by Coverity Scan; it wasn't my intention to question the design. But that is the usual problem with Coverity. Making the simple, obvious fix to correct a Coverity warning isn't necessarily the right way to deal with the issue. In this case, the linux man page says: ATTRIBUTES Multithreading (see pthreads(7)) The rexec() and rexec_af() functions are not thread-safe. so static is appropriate. cgf
Re: [PATCH] cygwin_rexec() returns pointer to deallocated memory
On Mon, May 26, 2014 at 10:39:03PM +0200, Peter Rosin wrote: On 2014-05-26 18:35, Christopher Faylor wrote: On Mon, May 26, 2014 at 04:27:10PM +0100, David Stacey wrote: On 26/05/14 14:36, Peter Rosin wrote: I believe the comment refers to if static is the right answer to the problem. Is there a need to handle concurrent calls? I can't really comment on that. As the code stands, neither of the two functions that we are discussing are reentrant. As long as the author and the user(s) of the routines are both aware of that then it isn't a problem. I was just trying to fix a coding error that was picked up by Coverity Scan; it wasn't my intention to question the design. But that is the usual problem with Coverity. Making the simple, obvious fix to correct a Coverity warning isn't necessarily the right way to deal with the issue. In this case, the linux man page says: ATTRIBUTES Multithreading (see pthreads(7)) The rexec() and rexec_af() functions are not thread-safe. so static is appropriate. Not thread-safe doesn't automatically mean that a following call may mess with what was returned from a prior call (by the same thread). But since it (IMHO) is a poor interface with no description of how to free any possibly allocated memory, I agree that static is the only viable option. The question was about reentrancy. AFAIK, reentrant doesn't mean that the buffer passed back from a call can't be subsequently modified by the thread. I'm not aware of any interface which enforces that behavior. cgf
Re: [PATCH] cygwin_rexec() returns pointer to deallocated memory
On Mon, May 26, 2014 at 05:40:49PM -0400, Christopher Faylor wrote: On Mon, May 26, 2014 at 10:39:03PM +0200, Peter Rosin wrote: On 2014-05-26 18:35, Christopher Faylor wrote: On Mon, May 26, 2014 at 04:27:10PM +0100, David Stacey wrote: On 26/05/14 14:36, Peter Rosin wrote: I believe the comment refers to if static is the right answer to the problem. Is there a need to handle concurrent calls? I can't really comment on that. As the code stands, neither of the two functions that we are discussing are reentrant. As long as the author and the user(s) of the routines are both aware of that then it isn't a problem. I was just trying to fix a coding error that was picked up by Coverity Scan; it wasn't my intention to question the design. But that is the usual problem with Coverity. Making the simple, obvious fix to correct a Coverity warning isn't necessarily the right way to deal with the issue. In this case, the linux man page says: ATTRIBUTES Multithreading (see pthreads(7)) The rexec() and rexec_af() functions are not thread-safe. so static is appropriate. Not thread-safe doesn't automatically mean that a following call may mess with what was returned from a prior call (by the same thread). But since it (IMHO) is a poor interface with no description of how to free any possibly allocated memory, I agree that static is the only viable option. The question was about reentrancy. AFAIK, reentrant doesn't mean that the buffer passed back from a call can't be subsequently modified by the thread. I'm not aware of any interface which enforces that behavior. Btw, the latest version of freebsd can't have this particular problem since ahostbuf is now gone. We probably should pull in the latest version into Cygwin's tree. cgf
Re: [PATCH] cygwin_rexec() returns pointer to deallocated memory
On Mon, May 26, 2014 at 05:46:10PM -0400, Christopher Faylor wrote: Btw, the latest version of freebsd can't have this particular problem since ahostbuf is now gone. We probably should pull in the latest version into Cygwin's tree. ...and that's apparently because Corinna added the code in question... cgf
Re: Bash silently truncates the Command Line when called programatically via CreateProcess as MAXPATHLEN was reduced to 8192 from 16384
On Mon, May 26, 2014 at 08:59:56PM +0530, Abhijit Bhattacharjee wrote: On a typical configuration, we use gmake on windows as the build system. GMAKE calls the Cygwin bash in order to invoke the MSVS compiler in-order to satisfy the dependency if a rule to call the compiler is present. If you're using Cygwin's make it will not truncate paths if it is running cygwin programs. Not sure what MSVS is. Now, for certain modules, the command line was seemingly getting truncated. On investigating further it revealed the reason for the truncation was because in the glob.cc, MAXPATHLEN was now defined as 8192 so, when bash was compiled with the changed crt code, the problem started to emerge. Now, it also seems that there was a discussion (https://cygwin.com/ml/cygwin-patches/2012-q1/msg00037.html) where Corinna mentioned about decreasing the size to 4096 and later increasing it to 8192. Unfortunately, for our case, 8192 is low a limit and ideally the previous limit of 16384 was working perfectly. The Argument that Corinna placed was because the default stack size is 2 Megs and sizeof(Char)==8, a local array of 8* 16384 would be too strenuous for the stack. It was still not clear to me as to why? 1. The Temporary buffer was not allocated on heap? The source code comes from FreeBSD. Managing this on the heap would mean a rewrite and would have its own problems. Since this isn't really an issue when Cygwin calls Cygwin programs it likely isn't really high on anyone's priority list. 2. Why the entire argument (both quoted and non-quoted string) was passed to the glob module. If instead, the argument string could had been tokeinized as interleaving quoted and non-quoted string, the restriction imposed on the argument length would be alleviated. What I am envisaging is, currently in the globify module, you are escaping all the quoted characters to demarcate from the non-quoted characters before calling glob once, so that the glob can only expand non-quoted sub-string. Instead, if we could call glob multiple times whenever we encounter a sub-string of non-quoted string, wouldn't it be cleaner? I don't really know what you're talking about but patches are always better than word descriptions. It sounds like you're using a non-Cygwin make to call a Cygwin process. If that is the case then it seems like the trivial fix is Don't Do That (tm) cgf -- 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
Re: Package file lists archive
On Sun, May 25, 2014 at 05:37:45PM -0500, Steven Penny wrote: The MSYS2 project keep an up to date archive with files lists for all packages http://downloads.sourceforge.net/project/msys2/REPOS/MINGW/x86_64/mingw64.files.tar.gz This file is not very large considering $ gzip -l mingw64.files.tar.gz compresseduncompressed ratio uncompressed_name 982852 9585152 89.7% mingw64.files.tar I was wondering if something like this is possible with Cygwin. Currently if you want to search a file that is not installed you must use cygcheck --package-query which I have noticed can be very slow. I would be happy to help with maintaining a Cygwin archive with file lists for all packages. Not sure how you'd do that. I suspect that MSYS is a lot more static than Cygwin. I don't think package maintainers wants to notify you every time they upload a package. And, frankly, I think it's a bad idea to keep a monolithic list of packages available for people to download anyway. -- 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
Re: Bash silently truncates the Command Line when called programatically via CreateProcess as MAXPATHLEN was reduced to 8192 from 16384
On Mon, May 26, 2014 at 03:38:13PM -0500, René Berber wrote: On 5/26/2014 3:08 PM, Christopher Faylor wrote: If you're using Cygwin's make it will not truncate paths if it is running cygwin programs. Not sure what MSVS is. Microsoft Visual Studio (or Something)? Probably. cgf -- 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
Re: [Question] about OS Support
On Mon, May 26, 2014 at 04:50:40AM +, tmorik...@abeam.com wrote: 1. MS SQL Server 2012 R2 is already supported ? As follows, it was written in the documentation. In [1.2. What versions of Windows are supported?] : Windows (XP/2003/Vista/2008/7/2008 R2/8/2012)* as of the time of writing this. We want to use the Cygwin on Windows Server 2012 R2. Yes, Cygwin works on Windows Server 2012. You can always install it to confirm this for yourself though. 2. Do you have a paid support or any support for Cygwin? We needs any support about Cygwin for any issues. http://www.redhat.com/services/custom/cygwin/ If you do go with Red Hat support remember that this is your mechanism for getting support. This mailing list doesn't support the Red Hat release. -- 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
Re: Rename detached debug info as cygwin1.dll.dbg
On Fri, May 23, 2014 at 04:05:34PM +0200, Corinna Vinschen wrote: On May 23 14:40, Jon TURNEY wrote: Not sure if this is wanted, and it obviously has some knock on effects on package and snapshot generation. But, cygport names detached debug info files by appending the .dbg suffix. This is 'obviously correct' as it means that both a foo.exe and foo.dll can exist and have detached debug info. For consistency, the attached patch changes the name of the detached debug info file for cygwin1.dll from cygwin1.dbg to cygwin1.dll.dbg As far as releases go, this is ok. I'll just have to tweak the next cygport file slightly. Chris might have to tweak the snapshot generation script as well, so he probably wants to chime in, too. It's more than just a tweak. I've known that there is a discrepancy for a long time but haven't considered it that big a deal. I'd prefer that this change not be made.
Re: Gdb with python enabled
On Thu, May 22, 2014 at 04:14:03AM +0200, Robin KERDILES wrote: I see cygwin doesn't provide gdb with python enabled : How should I do now ? Build gdb yourself with python enabled. cgf -- 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
Re: Problem running tcl/tk
On Tue, May 20, 2014 at 09:41:42AM +0400, Pavel Fedin wrote: I experience problem running tcl/tk applications. Attempt to do so results in: Wrong mailing list.
