From: chrubis@suse.cz
To: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 2/3] rpc01: moved common functions to a lib
Date: Tue, 8 Apr 2014 11:56:24 +0200 [thread overview]
Message-ID: <20140408095624.GA7530@rei.Home> (raw)
In-Reply-To: <5343A0AC.6010803@oracle.com>
Hi!
> But why to /usr/lib{,64}?
That depends on parameters passed to configure, in this case that was
rpmbuild %configure macro and rpm build system that reported unpackaged
files.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-04-08 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 15:25 [LTP] [PATCH 1/3] runtest/stress.part3: fix cmd for the rpc01 test case Stanislav Kholmanskikh
2013-12-23 15:25 ` [LTP] [PATCH 2/3] rpc01: moved common functions to a lib Stanislav Kholmanskikh
2013-12-23 15:25 ` [LTP] [PATCH 3/3] rpc01: fix compile-time warnings Stanislav Kholmanskikh
2014-02-05 12:08 ` chrubis
2014-04-07 18:12 ` [LTP] [PATCH 2/3] rpc01: moved common functions to a lib chrubis
[not found] ` <5343A0AC.6010803@oracle.com>
2014-04-08 7:12 ` [LTP] [PATCH] rpc01: moved the library into a separate directory Stanislav Kholmanskikh
2014-04-08 11:41 ` chrubis
2014-04-08 9:56 ` chrubis [this message]
2014-02-05 10:45 ` [LTP] [PATCH 1/3] runtest/stress.part3: fix cmd for the rpc01 test case Stanislav Kholmanskikh
2014-02-05 12:10 ` chrubis
2014-02-05 12:11 ` chrubis
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=20140408095624.GA7530@rei.Home \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=stanislav.kholmanskikh@oracle.com \
--cc=vasily.isaenko@oracle.com \
/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