I can't speak for the OP, but maybe because of an external toolchain? I
know that some dependencies (which are real dependencies, and should be
stated not just implied, even if normally not exposed by a build error)
only show up when using external toolchains, or at least that's most
even when I'v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Might be that it got introduced by configure because it detected
certain stuff on the host system or staging_dir thats normally not there.
It would help if the op could attach the config.log of wget.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG
On Tue, Nov 20, 2012 at 07:02:38PM +0100, michael-dev wrote:
> Index: net/wget/Makefile
> ===
> --- net/wget/Makefile (Revision 34280)
> +++ net/wget/Makefile (Arbeitskopie)
> @@ -22,7 +22,7 @@
> define Package/wget/Default
>S
Index: net/wget/Makefile
===
--- net/wget/Makefile (Revision 34280)
+++ net/wget/Makefile (Arbeitskopie)
@@ -22,7 +22,7 @@
define Package/wget/Default
SECTION:=net
CATEGORY:=Network
- DEPENDS:=+libpcre
+ DEPENDS:=+libpcre
