All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Help required to create recipe for FANN library
Date: Mon, 15 Jun 2009 14:41:39 -0400	[thread overview]
Message-ID: <4A3695E3.9070500@balister.org> (raw)
In-Reply-To: <1245088339.29153.39.camel@lenovo.internal.reciva.com>

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

Phil Blundell wrote:
> On Mon, 2009-06-15 at 21:34 +0400, Elvis Dowson wrote:
>> Hi,
>> 	When building the FANN library, I get the following message:
>>
>> NOTE: Multiple libraries (libfann.so.2, libdoublefann.so.2,  
>> libfixedfann.so.2, libfloatfann.so.2) found and LEAD_SONAME not defined
>>
>> What is the use of the LEAD_SONAME?
> 
> You should probably ignore LEAD_SONAME; this mechanism seemed like a
> good idea at the time but with hindsight it was not such a clever plan.
> The right way to fix this warning is to put each of the libraries in its
> own output package.

Do you have a hint on how to do that? I've had the same question.

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2009-06-15 18:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15  7:18 Help required to create recipe for FANN library Elvis Dowson
2009-06-15  9:45 ` Koen Kooi
2009-06-15 10:47   ` Elvis Dowson
2009-06-15 15:16     ` Philip Balister
2009-06-15 16:11       ` Elvis Dowson
2009-06-15 16:32         ` Leon Woestenberg
2009-06-15 17:23           ` Elvis Dowson
2009-06-15 17:31           ` Elvis Dowson
2009-06-15 17:34           ` Elvis Dowson
2009-06-15 17:52             ` Phil Blundell
2009-06-15 18:41               ` Philip Balister [this message]
2009-06-15 18:53                 ` Phil Blundell
2009-06-16  3:25                   ` Elvis Dowson
2009-06-16  7:22                     ` Phil Blundell
2009-06-15 19:39               ` Leon Woestenberg
2009-06-15 20:12                 ` Phil Blundell
2009-06-16  3:32                   ` Elvis Dowson

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=4A3695E3.9070500@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.