From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2 v2] libs: Hook up libs into the build system
Date: Fri, 8 Mar 2019 16:09:57 +0100 [thread overview]
Message-ID: <20190308150957.GA30032@dell5510> (raw)
In-Reply-To: <20190308140354.GC20072@rei>
Hi,
> And on my machine out-of-tree build does not managed to get past
> configure step, it fails somewhere in the ffsb configure step.
I often get
configure:2889: error: source directory already configured; run "make distclean" there first
So I build it with a bit drastic way:
rm -rfv *; git reset --hard; ./build.sh -o out
Kind regards,
Petr
next prev parent reply other threads:[~2019-03-08 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 12:42 [LTP] [PATCH 1/2 v2] Fix build with libnuma-dev on some distributions Cyril Hrubis
2019-03-08 12:42 ` [LTP] [PATCH 2/2 v2] libs: Hook up libs into the build system Cyril Hrubis
2019-03-08 13:05 ` Jan Stancek
2019-03-08 13:26 ` Petr Vorel
2019-03-08 13:28 ` Jan Stancek
2019-03-08 13:33 ` Cyril Hrubis
2019-03-08 14:03 ` Cyril Hrubis
2019-03-08 15:09 ` Petr Vorel [this message]
2019-03-08 15:10 ` Cyril Hrubis
2019-03-08 13:27 ` Cyril Hrubis
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190308150957.GA30032@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox