From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] problem building openswan using svn-buildroot
Date: Mon, 23 Feb 2009 15:44:56 +0100 [thread overview]
Message-ID: <874oyl2own.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090223143319.GA6299@cbg.dyndns.org> (Steffen Schulz's message of "Mon\, 23 Feb 2009 15\:33\:19 +0100")
>>>>> "Steffen" == Steffen Schulz <pepe_ml@gmx.net> writes:
>> Ok, anyone wants to step up and support openswan/strongswan?
>> Otherwise I think our users are better off if we remove the
>> package.
Steffen> I just updated a package I made a few months ago. It
Steffen> compiles and binaries seem to work, but I can not test it
Steffen> right now.
Ok.
Steffen> BTW, it happened the second time now that I could not use the most
Steffen> recent version of a program because the libtool patch won't apply.
Steffen> I used the most recent strongswan version that seems to work.
Steffen> The other package this happened with is gnutls > 2.4.2.
Yes, I've seen that as well. I think we need to come up with a more
robust way of handling the libtool stuff than blindly trying to apply
a patch to whatever version the package includes.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-02-23 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 1:21 [Buildroot] problem building openswan using svn-buildroot Robert Urban
2009-02-22 7:23 ` Peter Korsgaard
[not found] ` <49A17E91.7060104@unix-beratung.de>
2009-02-22 18:11 ` Peter Korsgaard
2009-02-23 10:28 ` Steffen Schulz
2009-02-23 11:14 ` Peter Korsgaard
2009-02-23 14:33 ` Steffen Schulz
2009-02-23 14:44 ` Peter Korsgaard [this message]
2009-02-24 6:14 ` Ulf Samuelsson
2009-02-24 7:20 ` Peter Korsgaard
2009-02-24 21:42 ` Ulf Samuelsson
2009-02-24 22:30 ` Peter Korsgaard
2009-02-25 5:40 ` Ulf Samuelsson
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=874oyl2own.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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