[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150519162224.GA6317@alex-ThinkPad-L530>
Date: Tue, 19 May 2015 18:22:24 +0200
From: Alex Dowad <alexinbeijing@...il.com>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] Build process uses script to add CFI directives to x86
asm
> configure already uses its own echo definition
> so ash's echo should not be used
> how did the config script end up calling ash's echo?
OK, thanks for pointing this out. I shouldn't have said that the problem was
with ash's echo.
The original configure script worked when I ran it on Linux Mint + bash, and didn't
work on Alpine Linux + BusyBox ash. I didn't notice echo() in the configure script,
did some experimentation with bash's echo and ash's, found a difference which seemed
to explain the observed problem, and worked around it.
Now it looks like the issue was something else. I can't seem to duplicate the problem
right this moment; however, the configure script as it is right now works on both
platforms.
Mysteries, mysteries...
AD
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
