From: Francesco RUNDO <francesco.rundo@st.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sf.net
Subject: Re: [LTP] [PATCH] cgroups: conditionally enable building cgroup tests
Date: Tue, 07 Jul 2009 08:53:12 +0200 [thread overview]
Message-ID: <4A52F0D8.7060509@st.com> (raw)
In-Reply-To: <364299f40907061028o4c9c2922ma7d430f5e03f4b38@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1442 bytes --]
Hi Garrett,
thanks for your comment. Below, my consideration:
Garrett Cooper wrote:
>On Mon, Jul 6, 2009 at 4:38 AM, Francesco RUNDO<francesco.rundo@st.com> wrote:
>
>
>>Hi Gowri,
>>
>>I've already fixed the same issue you reported. I've tested it successfully.
>>
>>Subrata has already merged my patch (please, find it in attachment).
>>
>>Please, check it before to submit another patch.
>>
>>
>
>At the end of the day, the real problem is that we're not using the
>--with- functionality in autoconf, e.g. --with-cgroups, and instead
>we're hacking a lot of noise into Makefile's.
>
Yes, you're right but your advice can't be applicable in the system in
which autoconf is not supported/used to build LTP (a possible scenario
in the embedded system).
>
>Also, you could have called SUBDIRS += once, like so:
>
>+SUBDIRS += cgroup cpuctl memctl io-throttle freezer cpuset
>
>I can tell at first glance that that Makefile is a mess anyhow,
>because it's referencing _hardcoded_ /proc references and as such will
>fail to cross-compile properly if the target or the host are setup
>differently from one another, in the following two scenarios:
>
Yes, check at "/proc" isn't safe as can't be applicable in case of
cross-compilation made off-line on the host.
I have provided a "work-around" patch to allow off-line
cross-compilation trying to reduce the number of changes to be applied
to the Makefile.
Regards
Francesco Rundo
[-- Attachment #1.2: Type: text/html, Size: 2124 bytes --]
[-- Attachment #2: Type: text/plain, Size: 390 bytes --]
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-07-07 6:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 10:15 [LTP] [PATCH] cgroups: conditionally enable building cgroup tests gowrishankar
2009-07-06 11:38 ` Francesco RUNDO
2009-07-06 12:00 ` gowrishankar
2009-07-06 12:42 ` Francesco RUNDO
2009-07-06 12:55 ` Subrata Modak
2009-07-06 13:05 ` Francesco RUNDO
2009-07-06 17:22 ` Garrett Cooper
2009-07-06 17:28 ` Garrett Cooper
2009-07-06 22:06 ` Mike Frysinger
2009-07-07 6:58 ` Francesco RUNDO
2009-07-07 14:24 ` Mike Frysinger
2009-07-08 7:40 ` Francesco RUNDO
2009-07-07 6:53 ` Francesco RUNDO [this message]
2009-07-07 9:11 ` Garrett Cooper
2009-07-06 15:51 ` Subrata Modak
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=4A52F0D8.7060509@st.com \
--to=francesco.rundo@st.com \
--cc=ltp-list@lists.sf.net \
--cc=yanegomi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.