From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add package linux-pam
Date: Fri, 10 Aug 2012 22:04:24 +0200 [thread overview]
Message-ID: <20120810220424.7aba837f@skate> (raw)
In-Reply-To: <CADiAo4+Ak_6ZLY0ND=ZYWz6wTsov4XnkpXvbK8ZSF-ukU7ALGw@mail.gmail.com>
Le Fri, 10 Aug 2012 06:30:49 -0400,
Dmitry Golubovsky <golubovsky@gmail.com> a ?crit :
> > This line is not needed, please remove.
>
> I removed it. However it is still there in few places:
>
> $ grep -rl "INSTALL_TARGET = YES" package/
> package/libglib2/libglib2.mk
> package/libgtk2/libgtk2.mk
Patches welcome :-)
> And surely install to target is needed for PAM (security modules)
Installation to target is enabled by default. From
package/pkg-generic.mk:
$(2)_INSTALL_STAGING ?= NO
$(2)_INSTALL_IMAGES ?= NO
$(2)_INSTALL_TARGET ?= YES
> > Instead of overriding LINUX_PAM_BUILD_CMDS, I would recommend using:
> >
> > LINUX_PAM_CONF_ENV += \
> > CC="$(TARGET_CC) -lintl -lfl"
>
> This gives me configure error "compiler cannot create executables" so
> I left this unchanged.
Try this instead:
ifeq ($(BR2_PACKAGE_LIBINTL),y)
LINUX_PAM_MAKE_OPT += LIBS=-lintl
endif
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-08-10 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 3:32 [Buildroot] [PATCH] Add package linux-pam Dmitry
2012-08-10 7:41 ` Thomas Petazzoni
[not found] ` <CADiAo4+Ak_6ZLY0ND=ZYWz6wTsov4XnkpXvbK8ZSF-ukU7ALGw@mail.gmail.com>
2012-08-10 10:51 ` Dmitry Golubovsky
2012-08-10 20:04 ` Thomas Petazzoni [this message]
2012-08-11 2:52 ` Dmitry Golubovsky
-- strict thread matches above, loose matches on Subject: below --
2012-08-11 2:50 Dmitry
2012-08-11 20:16 ` Thomas Petazzoni
2012-08-10 10:27 Dmitry
2012-08-22 7:09 ` Maxime Ripard
2012-08-23 1:53 ` Dmitry Golubovsky
2012-08-23 7:59 ` Maxime Ripard
2012-07-18 21:03 Dmitry
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=20120810220424.7aba837f@skate \
--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.