Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Chépied" <cedric.chepied@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ZNC: new package
Date: Sun, 09 Feb 2014 14:39:31 +0100	[thread overview]
Message-ID: <52f78515.2f24b40a.5600.ffffd4a7@mx.google.com> (raw)
In-Reply-To: <20140128195259.73158fe4@skate>

Dear Thomas,

At Tue, 28 Jan 2014 19:52:59 +0100,
Thomas Petazzoni wrote:
> Looking at the configure.ac from ZNC, it seems like the OpenSSL and
> Perl support is optional, and can be disabled using --disable-openssl
> and --disable-perl. It would probably be a good idea to use these to
> make these dependencies optional.

When I try to enable perl, configure fails. It uses the perl executable to
generate LDFLAGS but it does that with "my" executable (/usr/bin/perl) and then
tries to link with /usr/lib/perl5/core_perl/CORE/libperl.so which of course
fails.

For python, configure programs can use ./output/host/usr/bin/python2.7 but I
can't find the same for perl. I only find perl compiled for my target.

How can I fix this?

Regards,
-- 
C?dric Ch?pied
<cedric.chepied@gmail.com>

  reply	other threads:[~2014-02-09 13:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-04 22:59 [Buildroot] [PATCH] ZNC: new package Cédric Chépied
2014-01-05 10:07 ` Peter Korsgaard
2014-01-05 11:57   ` Cédric Chépied
2014-03-07 22:54     ` Thomas Petazzoni
2014-01-28 18:52 ` Thomas Petazzoni
2014-02-09 13:39   ` Cédric Chépied [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-01 21:53 Cédric Chépied
2014-01-02  8:59 ` Thomas Petazzoni
     [not found]   ` <52c542ae.87ad0e0a.3820.6636@mx.google.com>
2014-01-02 12:17     ` Thomas Petazzoni
2014-01-02  9:06 ` Jeremy Rosen

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=52f78515.2f24b40a.5600.ffffd4a7@mx.google.com \
    --to=cedric.chepied@gmail.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