From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] collectd: fix parallel build issues
Date: Mon, 6 Jul 2015 15:38:56 +0200 [thread overview]
Message-ID: <20150706153856.78ab447d@free-electrons.com> (raw)
In-Reply-To: <559A83B4.1010902@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 06 Jul 2015 10:33:40 -0300, Gustavo Zacarias wrote:
> > """
> > If _DEPENDENCIES is not supplied, it is computed by Automake. The
> > automatically-assigned value is the contents of _LDADD or _LIBADD, with
> > most configure substitutions, -l, -L, -dlopen and -dlpreopen options
> > removed. The configure substitutions that are left in are only
> > ?$(LIBOBJS)? and ?$(ALLOCA)?; these are left because it is known that
> > they will not cause an invalid value for _DEPENDENCIES to be generated.
> > """
> >
> > Best regards,
>
> Hi.
> That won't work in this case since it's added upon later (if
> BUILD_WITH_OWN_LIBOCONFIG ... ).
That same addition should be useless I believe:
collectd_LDADD += $(LIBLTDL) $(top_builddir)/src/liboconfig/liboconfig.la
collectd_DEPENDENCIES += $(top_builddir)/src/liboconfig/liboconfig.la
So LDADD already contains $(top_builddir)/src/liboconfig/liboconfig.la,
and LIBLTDL will be -lltdl, which will be ignored for foo_DEPENDENCIES.
But oh, well, maybe you don't want to fix the entire collectd build system :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-06 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 13:12 [Buildroot] [PATCH] collectd: fix parallel build issues Gustavo Zacarias
2015-07-06 13:22 ` Thomas Petazzoni
2015-07-06 13:33 ` Gustavo Zacarias
2015-07-06 13:38 ` Thomas Petazzoni [this message]
2015-07-06 13:43 ` Gustavo Zacarias
2015-07-06 13:48 ` Thomas Petazzoni
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=20150706153856.78ab447d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.