[PATCH] [test-suite] Make it build in more environments

Sergey Dmitrouk sdmitrouk at accesssoftek.com
Mon Feb 23 10:28:17 PST 2015


Ping.

On Mon, Jan 19, 2015 at 11:50:07AM +0200, Sergey Dmitrouk wrote:
> Ping.
>
> On Mon, Jan 12, 2015 at 10:22:33AM +0200, Sergey Dmitrouk wrote:
> > Ping.
> >
> > On Mon, Nov 24, 2014 at 06:50:05PM +0200, Sergey Dmitrouk wrote:
> > > Ping.
> > >
> > > On Fri, Nov 07, 2014 at 04:01:56PM +0200, Sergey Dmitrouk wrote:
> > > > Attached is typo correction to patch 0004, which is too big to include it
> > > > again.
> > > >
> > > > --
> > > > Sergey
> > > >
> > > > On Fri, Nov 07, 2014 at 03:46:52PM +0200, Sergey Dmitrouk wrote:
> > > > > Ping.
> > > > >
> > > > > Also attached one more small patch for shebang in *.tcl files of
> > > > > sqlite3 test.
> > > > >
> > > > > Regards,
> > > > > Sergey
> > > > >
> > > > > On Tue, Oct 28, 2014 at 09:20:58AM -0700, Sergey Dmitrouk wrote:
> > > > > > Hello,
> > > > > >
> > > > > > test-suite builds fine on a GNU/Linux machine against glibc and
> > > > > > other "standard" things, but I also need to build test-suite against
> > > > > > musl-libc and cross-compile it on Windows.  Making this happen required
> > > > > > some modifications in test-suite, which generally make it work in a
> > > > > > wider range of environments.
> > > > > >
> > > > > > I have ten patches so far, it's quite a lot and they are not very
> > > > > > related.  Sending them separately would basically require ten
> > > > > > separate emails, but wouldn't make review much easier.  I'll separate
> > > > > > them if it's preferable.
> > > > > >
> > > > > > A couple of comments:
> > > > > >
> > > > > > 1. There is one huge patch that includes changes in the configure
> > > > > >    script.  Even using autoconf 2.60 didn't help much, though it reduced
> > > > > >    number of changed lines by about 25%.
> > > > > > 2. Some changes are related to escaping.  As I see it no one cares about
> > > > > >    paths with spaces (no explicit escaping, so it doesn't work), hence
> > > > > >    new changes shouldn't break anything.
> > > > > >
> > > > > > Please find attached patches.  Most changes are quite trivial, so as
> > > > > > they are not related to each other, patches that look good can be
> > > > > > committed while I'm updating those that are not OK (no commit access, so
> > > > > > please help me with that).
> > > > > >
> > > > > > Best regards,
> > > > > > Sergey



More information about the llvm-commits mailing list