bug-libunistring
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-libunistring] heads up: libunistring-0.9.10: config.sub broken?


From: gabriele balducci
Subject: Re: [bug-libunistring] heads up: libunistring-0.9.10: config.sub broken?
Date: Mon, 28 May 2018 17:23:55 +0200

hi

> It works for me.
>
> You need to check the configure command that you gave, as well as environment
> variables such as CC, CFLAGS, CPPFLAGS, LDFLAGS, LIBS, LD_LIBRARY_PATH, and r
> ead
> the reference documentation [1].
>
> So, what was this command and the relevant environment variable values?
>
> If you did not specify a system name, what matters is config.guess, not confi
> g.sub.
> Then please also show the result of invocations such as
>   $ env CC=gcc build-aux/config.guess


first of all thanks a lot for taking the time to reply

I think I have figured out what the problem was: I'm using the very
latest alpha bash (5.0-alpha) and there this bug:
https://www.mail-archive.com/address@hidden/msg21417.html

Basically: in bash-5.0-alpha, in POSIX mode, assignments preceding
'read' incorrectly persist past the command.

Now, all the shell scripts for the build are run in posix mode, no?
shebang is #!/bin/sh everywhere

So, in this fragment of config.sub:

  # Split fields of configuration type
  IFS="-" read -r field1 field2 field3 field4 <<EOF
  $1
  EOF

IFS keeps its "-" value past the read command, where it shouldn't.

This makes the following test:

  if [ x$os != x ]

fail with:

  [: too many arguments

(because os's value is linux-gnu and this gets splitted into 2 words
due to the (wrong) IFS value). I missed that error message when I sent
my first email.

The final result is that os gets screwed to "none" and I get the
related mess

Running the libunistring-0.9.10 build with bash-4.4pl19 works smoothly,
as always: OS is correctly guessed and shared libs are installed and
everything is fine.

It isn't clear to me why running autogen.sh fixes things even with the
buggy bash-5.0-alpha, but I'm quite sure that the problem was that.

So, thanks a lot again and apologies for the noise

ciao
gabriele




reply via email to

[Prev in Thread] Current Thread [Next in Thread]