X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; q=
	dns; s=default; b=cWENucGLWI5K37/ZA6q0gZJ9PJP+055kM+6GPJXWPUGCLw
	dq+MsfjNc3bWhIccqrmA2y+0PTolhbn9VPDYEom5WD+oEum+VxJI5azxuA/dD05L
	/A5mp21mWPctLz/fDz4W6xgC3WUJiAukvMNrKufz63bTXOgOi4ZCxPnW9XTck=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; s=
	default; bh=4vX2wPHDmtp406zrhChyLtz8jWs=; b=M8MHmmHwYzJlTKqC1exR
	XmmlakrHSozRbc6zVLDnSV9NEjmYRP6roVczTJhZ0ZynvgS1PC8W3q4Z3fneqxNJ
	DF8lNY8UJikRDGErpklvcjv/vvWGDlV4v2F+pO7irICYBU6+GXZdYIk1he8dp8MO
	fmnNX72PNvU41ftQE9empiA=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-0.1 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_FAIL,SPF_HELO_PASS,URI_HEX autolearn=no version=3.3.1 spammy=tweak, Frame
X-HELO:	n5.nabble.com
Date:	Mon, 15 Jul 2019 06:42:28 -0700 (MST)
From:	rih3306 <rob DOT hickey AT us DOT bosch DOT com>
To:	cygwin AT cygwin DOT com
Message-ID:	<1563198148321-0.post@n5.nabble.com>
In-Reply-To:	<aa560db2-2a18-e16f-5f86-ee2dab743d45@SystematicSw.ab.ca>
References:	<1562880320576-0 DOT post AT n5 DOT nabble DOT com> <b595740e-3e01-8a22-2a77-c9af96560931 AT gmail DOT com> <aa560db2-2a18-e16f-5f86-ee2dab743d45 AT SystematicSw DOT ab DOT ca>
Subject:	Re: building expect problems on W10
MIME-Version:	1.0
X-IsSubscribed:	yes

Good suggestion thank you.

Can we please consider where I'm at presently before trying that?

I'm now able to build expect.exe and libexpect5.45.4.dll using this
configure line


./configure --disable-option-checking '--prefix=/usr/local' 
'--build=x86_64-unknown-cygwin' 'CC=/cygdrive/C/work/usr/local/bin/gcc'
'CFLAGS=-mcmodel=large' 'build_alias=x86_64-unknown-cygwin'
--cache-file=../config.cache --srcdir=. &>configure-out.txt


followed of course by make.

However,  running ./expect.exe produces a stackdump

which is here.

  Exception: STATUS_ACCESS_VIOLATION at rip=00000000000
rax=0000000000000000 rbx=0000000000800080 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=000000006D655AD3
r8 =0000000000000000 r9 =000000006CDEE551 r10=0000000000000000
r11=8101010101010100 r12=0000000000867580 r13=0000000000867590
r14=00000000008644F0 r15=0000000000867590
rbp=0000000000875EC0 rsp=00000000FFFFCA08
program=C:\work\___packages\expect\expect5.45.4\expect.exe, pid 940, thread
main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame        Function    Args
End of stack trace
 


I get the stackdump both with and without the memory model option in the
configure line.

Is it possible to tweak my configure line and get rid of the stackdump?

Thank you.



--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html

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

- Raw text -