public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* building expect problems on W10
@ 2019-07-11 21:25 rih3306
  2019-07-11 23:10 ` René Berber
  0 siblings, 1 reply; 4+ messages in thread
From: rih3306 @ 2019-07-11 21:25 UTC (permalink / raw)
  To: cygwin

I'm having trouble building expect. 

I'm using W10 + cygwin + GCC 9.1.0

$ uname -a
CYGWIN_NT-10.0  GZ1CB  2.11.2(0.329/5/3) 2018-11-08 14:34 x86_64 Cygwin

using this configure line
./configure --build=x86_64-unknown-cygwin  
CC=/cygdrive/C/work/usr/local/bin/gcc  --cache-file=config.cache 
&>expect-configure-out.txt

Configure output includes
 
This script, last modified 2003-10-07, has failed to recognize
the operating system you are using. 

Where do I start, suggestions?

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: building expect problems on W10
  2019-07-11 21:25 building expect problems on W10 rih3306
@ 2019-07-11 23:10 ` René Berber
  2019-07-12 16:07   ` Brian Inglis
  0 siblings, 1 reply; 4+ messages in thread
From: René Berber @ 2019-07-11 23:10 UTC (permalink / raw)
  To: cygwin

On 7/11/2019 4:25 PM, rih3306 wrote:

> I'm having trouble building expect. 
> 
> I'm using W10 + cygwin + GCC 9.1.0
> 
> $ uname -a
> CYGWIN_NT-10.0  GZ1CB  2.11.2(0.329/5/3) 2018-11-08 14:34 x86_64 Cygwin

That's an odd combination, an ancient version of Cygwin with a new gcc
(which you probably built).

> using this configure line
> ./configure --build=x86_64-unknown-cygwin  
> CC=/cygdrive/C/work/usr/local/bin/gcc  --cache-file=config.cache 
> &>expect-configure-out.txt

Why are you configuring like a cross-compilation?

None of that should be needed to build a package that is to be used in
the current version.

> Configure output includes
>  
> This script, last modified 2003-10-07, has failed to recognize
> the operating system you are using. 

Configure usually shows "Target: x86_64-pc-cygwin", but yes the log also
shows "host='x86_64-unknown-cygwin'".  Anyway that is using configure
without any build, or host parameter.
-- 
R.Berber


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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: building expect problems on W10
  2019-07-11 23:10 ` René Berber
@ 2019-07-12 16:07   ` Brian Inglis
  2019-07-15 13:42     ` rih3306
  0 siblings, 1 reply; 4+ messages in thread
From: Brian Inglis @ 2019-07-12 16:07 UTC (permalink / raw)
  To: cygwin

On 2019-07-11 17:09, René Berber wrote:
> On 7/11/2019 4:25 PM, rih3306 wrote:
>> I'm having trouble building expect. 
>> I'm using W10 + cygwin + GCC 9.1.0
>> $ uname -a
>> CYGWIN_NT-10.0  GZ1CB  2.11.2(0.329/5/3) 2018-11-08 14:34 x86_64 Cygwin
> That's an odd combination, an ancient version of Cygwin with a new gcc
> (which you probably built).
>> using this configure line
>> ./configure --build=x86_64-unknown-cygwin  
>> CC=/cygdrive/C/work/usr/local/bin/gcc  --cache-file=config.cache 
>> &>expect-configure-out.txt
> Why are you configuring like a cross-compilation?
> None of that should be needed to build a package that is to be used in
> the current version.
>> Configure output includes
>> This script, last modified 2003-10-07, has failed to recognize
>> the operating system you are using. 
> Configure usually shows "Target: x86_64-pc-cygwin", but yes the log also
> shows "host='x86_64-unknown-cygwin'".  Anyway that is using configure
> without any build, or host parameter.

Install cygport, the current Cygwin expect src package, upgrade Cygwin and all
packages that don't conflict with your local builds.

Untar the src package, and use cygport to build expect under Cygwin, as it takes
care of dependencies and quirks, from the directory containing the cygport file:

	$ cygport expect.cygport download all

which should build without errors.

Then you can update the expect version in expect.cygport and retry with the
latest source version.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: building expect problems on W10
  2019-07-12 16:07   ` Brian Inglis
@ 2019-07-15 13:42     ` rih3306
  0 siblings, 0 replies; 4+ messages in thread
From: rih3306 @ 2019-07-15 13:42 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-07-15 13:42 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-11 21:25 building expect problems on W10 rih3306
2019-07-11 23:10 ` René Berber
2019-07-12 16:07   ` Brian Inglis
2019-07-15 13:42     ` rih3306

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).