DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 52ABhQrp2723812
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 52ABhQrp2723812
Authentication-Results:	delorie.com;
	dkim=fail reason="signature verification failed" (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=lskO9vhf
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 3DEA63858C66
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1741607004;
	bh=JJPjk2p22YUefp7yFVlTB5Pe5Yew6tNxyRQ0Qh9Gszk=;
	h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post:
	List-Help:List-Subscribe:From:Reply-To:From;
	b=lskO9vhfD7nQfAsWwxSKRiKfInxsaUEQbg6Dp3sq9/tlXXmR6U6myqTLnxcBPlano
	bXMexXvb3MvMcAGIw3392HGh3JmJbgWK9YQlyMMKsHZMNMCDrBZCJE5h28g0WzWoSg
	0X9pqIes2ZYComh2Tu35Ivj3Qmn6TWhwxTPXwP7Q=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org E464A3858D20
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org E464A3858D20
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1741606942; cv=none;
	b=l6Ck97XlJkH8OEySgvSAMWzUCwi4DNTMbUlVb6sNcUUY8IdLAwnpmIB/5oMoLZQF+V7XY37ruRtK6t8iQ6j8IexeloEN5PRfHKsrWSSB7D9PhPFa+KZABpt7F143h5/CdcRodJRrHRkav55H1YVIjhvMl7wEfsIkAPgvg5CND3M=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1741606942; c=relaxed/simple;
	bh=JpraeI1FTanYMsmu55qOdlruH+SLr9ItUUQdYE4k3HM=;
	h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version;
	b=g4VVWUgnrM8hkCKsch3XRZie48WwAq7wRx0rGAhzwwKPgah4FkqAr0L+5yJT8rvpIYQPNtjmZL0HMBh2mtVmw63hFSxFsYPx6jBbslX4EM7ZClcYPYZqGTxMg1H+CLDcBLUxKdJF4Ot1TkbtGdMJpI0FI8/VSz9N+4h4tjUhIzs=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org E464A3858D20
To:	Brian DOT Inglis AT SystematicSW DOT ab DOT ca, cygwin AT cygwin DOT com, camm AT maguirefamily DOT org
Subject:	Re: GCL and dependencies on cygwin
Date:	Mon, 10 Mar 2025 07:42:14 -0400
Message-ID:	<87tt815cyx.fsf@glory.maguirefamily.org>
MIME-Version:	1.0
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Camm Maguire via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Camm Maguire <camm AT maguirefamily DOT org>
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

Greetings, and thank you so much for your helpful reply!

Brian Inglis via Cygwin wrote:

> On 2025-03-09 08:16, Camm Maguire via Cygwin wrote:
> > Greetings, and thank you all for your work on this system.
> > 1) I am preparing a set of GCL releases, both of which basically work on
> > latest cygwin, but the signal handling seems to have been recently
> > broken.  Specifically, GCL can trap and handle SIGFPE when these
> > exceptions are enabled.  Under gdb, the signal appears, but then a
> > SIGTRAP is caught in kernel.dll under secure_getenv(), and the handler
> > is never called.  Thoughts?
> 
> Which release?
> 
>                       $ uname -srvmo
> 
> If current stable 3.5.7, try the latest 3.6.0-0.42?.g* test releases, which have 
> a number of signal handling fixes and improvements, still being reworked to 
> conform to more specs and expected operation, with hundreds of 
> processors/threads, and thousands of concurrent processes/threads used at some 
> large European research institutes.
>

This was stable (3.5.7), but I've retried with latest testing (.423) and
the problem persists.  Given secure_getenv in the backtrace, I'm
wondering if there is some sort of permissions issue here?  Don't know
if there is a direct analog of su/sudo, but tried opening a terminal or
emacs as 'administrator' and no luck.  As I mentioned before, as memory
serves, this worked in the past, i.e. several years ago.

> > 2) I am considering volunteering as a maintainer.  I see the docs
> > describing the procedure.  I maintain some packages for Debian, and
> > wondering if there was any simplification in avoiding duplicate work
> > here.
> 
> Some Cygwin packagers/maintainers also develop or support the packages on other 
> distros.
> 
> Cygwin has some common heritage from Fedora like policies, similar to DFSG, 
> package naming, and usages like -devel and -debuginfo vs -dev or -dbg, but 
> *cygport* is closer to Gentoo portage ebuilds, implemented in bash, and for some 
> packages can do a lot of rote grunt work for you, that you have to explicitly 
> define for Debian etc.
> 
>                       https://cygwin.com/git/cygwin-packages/
> 
> for example:
> 
>                       https://cygwin.com/git/?p=git/cygwin-packages/clisp.git;a=summary
> 
>                       https://cygwin.github.io/cygport/toc_index.html
> 
> or install cygport and access:
> 
>                       $ cygstart /usr/share/doc/cygport/html/manual/toc_index.html
> 
> which should open the docs in your default Windows browser.
> 
> For new ports or modernizing adopted packages, I hacked a script to check Fedora 
> and OpenSuSE sources for spec files, download if not already available locally, 
> and do a "good enough" ~90% conversion to cygport.
> 
> So far, for only a few Debian sources, I found it easier to download the debian/ 
> directory, cat or cp the relevant files (mostly dsc, control, and rules) then 
> cygport-ize or Cygwin-ize the contents.
> But you may find it helps you adapt if you hack your own download and conversion 
> script in your favourite associative memory language.
> 
> I have also found Fedora, OpenSuSE, and Debian sources useful for patches.
> 
> In general, these topics are best discussed on cygwin-apps, to which all 
> packagers, maintainers, and contributors are expected to subscribe.
>

Thanks so much -- I will carry this conversation there.  But in general
the first step is the same, i.e. to upload sources to a pubic area and
get approval from an existing maintainer?

Take care,
-- 
Camm Maguire			     		    camm AT maguirefamily DOT org
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

-- 
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

- Raw text -