On 2016-01-09 21:58, Heinrich Schuchardt wrote:
> Fixes #21567
>
> Since commit e49896f232ed2ed76f6a67cfb6c4f9bc3ac01af
> package/libs/libtool: rename to libltdl
> we see warnings like
>
> "WARNING: No feed for package 'libtool' found, maybe it's already part of
> the standard packages?"
>
> for
The upshot of what I've figure out is that this patch is the correct
one; because BUILD_DEPENDS depends on 'source package name' AND 'source
package name' is the last part of the subdir (i.e. for network/openvpn
it would be openvpn) in which the package resides, libltdl is the new
'source pack
Actually it turns out I was right: This depends on 'source' package not
binary package, therefore the patch I am verifying (doing a test SDK
compile to verify nothing broke) is required.
Regards,
Daniel
On 09/01/16 04:15 PM, Daniel Dickinson wrote:
Never mind, I'm confusing source package an
Never mind, I'm confusing source package and binary package; I'm not
sure which this particular use depends on.
Regards,
Daniel
On 09/01/16 04:07 PM, Daniel Dickinson wrote:
I do not believe this is the right fix:
The PKG_NAME is libtool so the the package name
should be found as libtool not
I do not believe this is the right fix:
The PKG_NAME is libtool so the the package name
should be found as libtool not libltdl.
I have a patch I am testing that fixes the metadata.pm
issue and will correctly use libtool as the soure
package name.
Regards,
Daniel
On 09/01/16 03:58 PM, Heinrich
Fixes #21567
Since commit e49896f232ed2ed76f6a67cfb6c4f9bc3ac01af
package/libs/libtool: rename to libltdl
we see warnings like
"WARNING: No feed for package 'libtool' found, maybe it's already part of
the standard packages?"
for packages with PKG_FIXUP:=libtool.
Build dependencies for libtool a
