All of lore.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring at users.sourceforge.net>
To: powertop@lists.01.org
Subject: Re: [Powertop] Complete build options for Pthread API
Date: Mon, 20 Oct 2014 06:44:57 +0200	[thread overview]
Message-ID: <54449349.2000400@users.sourceforge.net> (raw)
In-Reply-To: CAG27Bk0EgYDVvoPPoqqSP1UwmVuLpL_ax1Z4fwmLAYSdtM9ZHw@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 2431 bytes --]

> I don't know what sort of adjustments you have in mind.

I suggest a bit more fine-tuning for the explanation.


> The variables are in commit body, so I am assuming people who read code
> can see them without explicit note about them.

I would prefer a commit message that will also be useful to some degree without
reading the affected source code.


> But if you insist improvement with the message could you write what you
> would like to see so that I can include it without confusions.

You can see from a few contributions for other software that I used a wording
like the following:

The configuration script "AX_PTHREAD" was added to the build specification
so that corresponding special parameters will be taken into account.
http://www.gnu.org/software/autoconf-archive/ax_pthread.html



You might be still interested to stress other details for your PowerTop testers
and reviewers.



>>> +AX_PTHREAD([], [AC_MSG_ERROR([Could not configure pthreads support])])
>>
>> 2. You chose to pass an empty "ACTION-IF-FOUND". Would it make sense to
>> restructure this place a bit in the configuration script so that the
>> following statements will be directly used by the first macro parameter?
> 
> That would make powertop m4 code copy to drift from version provided by
> autotools-archive, making the upstream fixes to incompatible. I strongly
> recommend against adding additional maintenance cost to this sort of stuff.

I do not really understand the intention in this feedback.


How do you think about the following statement layout at the discussed script place?

diff --git a/configure.ac b/configure.ac
index 4991d97..0ebe69d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -128,11 +128,12 @@ AS_IF([test "$has_libpci" -eq 0], [
 	])
 ])

-AC_SEARCH_LIBS([pthread_create], [pthread], [], [
-	AC_MSG_ERROR([libpthread is required but was not found])
-], [])
-AC_SEARCH_LIBS([inet_aton], [resolv], [], [
-	AC_MSG_ERROR([libresolv is required but was not found])
-], [])
-
-AC_OUTPUT
+AX_PTHREAD([LIBS="$PTHREAD_LIBS $LIBS"
+CFLAGS="$CFLAGS $PTHREAD_CFLAGS"
+CC="$PTHREAD_CC"
+AC_SEARCH_LIBS([inet_aton],
+               [resolv],
+               [AC_OUTPUT],
+               [AC_MSG_ERROR([libresolv is required but was not found])],
+               [])],
+           [AC_MSG_ERROR([Could not configure pthreads support])])


Regards,
Markus

             reply	other threads:[~2014-10-20  4:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20  4:44 SF Markus Elfring [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-01  8:15 [Powertop] Complete build options for Pthread API SF Markus Elfring
2014-10-31 18:01 Alexandra Yates
2014-10-31 10:20 SF Markus Elfring
2014-10-31 10:01 Sami Kerola
2014-10-31  3:35 Alexandra Yates
2014-10-31  2:34 Alexandra Yates
2014-10-25 10:18 Sami Kerola
2014-10-25  8:58 Sergey Senozhatsky
2014-10-22 14:33 Sami Kerola
2014-10-22 12:41 Sergey Senozhatsky
2014-10-22  9:41 Sami Kerola
2014-10-19 18:18 Sami Kerola
2014-10-19 11:30 SF Markus Elfring
2014-10-18 22:57 Sami Kerola
2014-10-18 19:20 SF Markus Elfring

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=54449349.2000400@users.sourceforge.net \
    --to=powertop@lists.01.org \
    /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.