mailing list of musl libc
 help / color / mirror / code / Atom feed
From: naruto canada <>
Subject: [musl] anyone know how to approach this problem (expect5.x.x hangs)
Date: Fri, 25 Feb 2022 17:59:26 +0000	[thread overview]
Message-ID: <> (raw)


I'm in the process of porting all my desktop env. over to musl.
I'm about 70% done. I hit a few minor snags but got over them.
I had expected a lot more painful experience, but it turned out ok.
I could not get xserver to compile but will work around using vnc for now.
I am quite happy I got qemu to compile.
The last 30% (Browsers !!!), I dare not approach them right now.

Anyway, back to my probem, expect5.x.x hangs,
no seg fault, so I do not know how to approach this problem.
normally I do a simple test:
expect -c "spawn ls" # this always succeeds.

(I use expect to automate password creation)
VNCRP=123456 # need 6 characters # create ~/.vnc/passwd
echo '#!/usr/bin/expect
set timeout -1
spawn vncpasswd
expect "Password:"
send "'$VNCRP'\r"
expect "Verify:"
send "'$VNCRP'\r"
expect "Would you like to enter a view-only password (y/n)?"
send "n\r"
interact' > /tmp/p.ex
expect /tmp/p.ex
This script works fine under glibc, but hangs under musl.

I've already tried the same version of expect and patches from
I got the same result. (it hangs)

This is not a priority problem for me. I can easily work around it
without using expect.
Just wondering if anyone know how to approach this problem (when there
is no seg fault)

             reply	other threads:[~2022-02-25 17:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 17:59 naruto canada [this message]
2022-02-25 19:35 ` [musl] " naruto canada
2022-02-25 23:32   ` Rich Felker
2022-02-26  2:46     ` naruto canada
2022-02-26 13:48       ` Rich Felker
2022-02-27 15:35         ` naruto canada
2022-02-27 21:29           ` naruto canada
2022-02-28  0:16             ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

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 NNTP newsgroup(s).