Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kinsella, Ray <ray.kinsella@intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] package/radlib: new package
Date: Sun, 24 Apr 2016 15:15:16 +0000	[thread overview]
Message-ID: <1461510916.5247.21.camel@intel.com> (raw)
In-Reply-To: <57195C19.3070307@mind.be>

Thanks Arnout, 

See inline. 

On Fri, 2016-04-22 at 01:02 +0200, Arnout Vandecappelle wrote:
>   Please generate patches with the -N option; the 1/3 becomes invalid
> when a 4th 
> patch is added, or when some of the patches are accepted upstream.


ok then, so it should be a git format-patch -N. I see what you mean,
you may want to remove the patches independently as they get
upstreamed, so that would muck up the numbering. 

> Given 
> upstream's lack of updates the latter isn't very likely :-) Did you
> try to 
> submit the patches upstream?

Haven't submitted them upstream yet, on my to do list. 

>   Since the AM_CONDITIONAL is defined just above, it's better to use
> AM_COND_IF:
> 
> AM_COND_IF([PGRESQL],
>    PKG_CHECK_MODULES([POSTGRESQL], [libpq])
> )

ok, thanks for the tip.

> 
> (untested, of course).
> 
> > ++  PKG_CHECK_MODULES([POSTGRESQL], [libpq])
> > ++fi
> > +
> > + AC_ARG_ENABLE(sqlite,
> > + [  --enable-sqlite                include radlib sqlite database
> > support],
> > +@@ -32,6 +35,9 @@ AC_ARG_ENABLE(sqlite,
> > +   *) sqlite=false ;;
> > + esac],[sqlite=false])
> > + AM_CONDITIONAL(SQLITE, test x$sqlite = xtrue)
> > ++if test x$sqlite = xtrue; then
> 
>   Same here.

ok

> 
>   Same, use AM_COND_IF

ok

>   I guess there should be an error in the else branch?

makes sense.

>   I think this should be the first patch; our autoreconf will not be
> happy 
> without subdir-objects.

autoreconf does complain without the subdir-objects. The removal of the
CROSS_COMPILE in the same patch is important as the linker breaks
without it. It won't even get to linking stage if it can't find the
various database libraries fixed in the two previous patches.

Suggest a new first patch to fix sudir-objects (patch number 4.), but
then leave the other patches as they are. So the flow would be.

1. Fix subdir-objects
2. Fix sqlite + postgresql
3. Fix mysql
4. Fix the linker (CROSS_COMPILE).

What do you think?

+
> > + AM_INIT_AUTOMAKE([radlib],[2.12.0])
> 
>   Shouldn't this one be removed?
yup

>   Lines in help text should be wrapped at 72 columns, where tab
> counts for 8.

ok - I will investigate

>   I'm not really happy with this choice, I'd prefer an automatic
> selection. But 
> it's true, if both mysql and postgresql are selected it's hard to
> decide which 
> one should be used...

sent a seperate email on this.
mysql and postgresql are mutually exclusive.
sqlite lite can be safely enabled/disable depending on
BR2_PACKAGE_SQLITE.

> 
>   Err, I see sha1 and md5 there, but not sha256. So you should take
> the md5 and 
> sha1 from sourceforge and add the locally-calculated sha256.

ok 


> > +sha256 
> >  82b98bb5e08a500dea1e4252843b9c772fa1fb67ac8ab89ed64abdd5e22eca66 
> >  radlib-2.12.0.tar.gz
> RADLIB_DEPENDENCIES += sqlite
> else
> RADLIB_CONF_OPTS += --disable-sqlite

ok

> > +endif
> > +
> > +ifeq ($(BR2_PACKAGE_RADLIB_MYSQL),y)
> > +RADLIB_CONF_ENV=ac_cv_path_MYSQL_CONFIG="$(STAGING_DIR)/usr/bin/my
> > sql_config"
> > +RADLIB_CONF_OPTS += --enable-mysql
> 
>   Same here

ok

> 
> > +endif
> > +
> > +ifeq ($(BR2_PACKAGE_RADLIB_POSTGRESQL),y)
> > +RADLIB_CONF_OPTS += --enable-pgresql
> 
>   Same here

ok

Thanks,

Ray K

  reply	other threads:[~2016-04-24 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 16:06 [Buildroot] [PATCH v5] package/radlib: new package ray.kinsella at intel.com
2016-04-13 16:06 ` ray.kinsella at intel.com
2016-04-21 23:02   ` Arnout Vandecappelle
2016-04-24 15:15     ` Kinsella, Ray [this message]
2016-05-02 20:44       ` Arnout Vandecappelle
2016-06-14 14:20         ` Kinsella, Ray
2016-04-20 15:44 ` Kinsella, Ray
2016-04-20 15:59   ` Thomas Petazzoni
2016-04-24 14:49     ` Kinsella, Ray

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=1461510916.5247.21.camel@intel.com \
    --to=ray.kinsella@intel.com \
    --cc=buildroot@busybox.net \
    /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