Hi,
I found that openssl did not compile on the uml target under x86_64. The
attached patch should
correct this and is working for me. Is this the right way to do it?
thanks,
Thomas
Index: package/openssl/Makefile
===
--- package/
I'd like to do a whole root pivot and then an overlay on top of that.
Do the current preinit hooks support that?
- Ryan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Dear All,
I have a curious shop issue in trunk with my tp-link wr1043nd. When I
connect my pc to The router it receives a dhcp lease and ip address without
issues. If I reboot the pc, the same happens, no issues. When I reboot the
router however, the pc does not receive a dhcp lease from the route
Hi,
On Sunday 15 April 2012 23:19:31 Ashkanull wrote:
> my wr941nd uses a MARVELL 88e6063 Swtich and I have these lines in
> backfire/build_dir/linux-ar71xx/linux-2.6.32.27/.config in r31251
> seems it should support dot1q and vlaning as well
>
> CONFIG_NET_DSA=y
> # CONFIG_NET_DSA_TAG_DSA is not
On Thursday 19 April 2012 22:42:32 Jonas Gorski wrote:
> On 19 April 2012 22:32, Florian Fainelli wrote:
> > Hi Arend,
> >
> > On Thursday 19 April 2012 21:44:43 Arend van Spriel wrote:
> >> Hi Hauke,
> >>
> >> I have setup openwrt environment and can build a router image. The
> >> kernel comes
On 19 April 2012 22:32, Florian Fainelli wrote:
> Hi Arend,
>
> On Thursday 19 April 2012 21:44:43 Arend van Spriel wrote:
>> Hi Hauke,
>>
>> I have setup openwrt environment and can build a router image. The
>> kernel comes from a tarball. Do you or someone else ever tried to pull
>> in the kerne
Hi Arend,
On Thursday 19 April 2012 21:44:43 Arend van Spriel wrote:
> Hi Hauke,
>
> I have setup openwrt environment and can build a router image. The
> kernel comes from a tarball. Do you or someone else ever tried to pull
> in the kernel from a git repository? I want to look into this myself,
Hi Hauke,
I have setup openwrt environment and can build a router image. The
kernel comes from a tarball. Do you or someone else ever tried to pull
in the kernel from a git repository? I want to look into this myself,
but could use some pointers.
Gr. AvS
On 04/19/2012 05:41 AM, Mirko Vogt wrote:
I also noticed complains about glibc - however every time I ask people
why in particular they chose glibc over eglibc I didn't get any
meaningful response. glibc is de facto unmaintained in OpenWrt and I'd
actually like to purge it out - still I'm afraid
Hey all,
as a matter of fact glibc support is currently unmaintained in OpenWrt
and I'd like to drop it entirely.
We received quite some complains about buggy/non-working glibc support -
most people however got happy with using eglibc in the end (which is
supported quite well).
However, before pur
Le 19/04/2012 16:40, Mirko Vogt a écrit :
On 04/19/2012 04:00 PM, Emmanuel Deloget wrote:
Good catch. In fact, HEAD is likely to never be the right choice, even
in other packages. So maybe we can forbid it?
That's what I meant with:
"Since fetching the latest HEAD of any external source is unc
On 04/19/2012 04:00 PM, Emmanuel Deloget wrote:
> Good catch. In fact, HEAD is likely to never be the right choice, even
> in other packages. So maybe we can forbid it?
That's what I meant with:
"Since fetching the latest HEAD of any external source is uncommon and
to be avoided anyway (since buil
Le 19/04/2012 15:02, Mirko Vogt a écrit :
On 04/19/2012 11:43 AM, Emmanuel Deloget wrote:
Force the use of known revision for specific eglibc versions.
Eglibc revision can only be changed if the user selects the trunk
version.
Signed-off-by: Emmanuel Deloget
Index: toolchain/eglibc/Config.in
=
On 04/19/2012 11:43 AM, Emmanuel Deloget wrote:
> Force the use of known revision for specific eglibc versions.
> Eglibc revision can only be changed if the user selects the trunk
> version.
>
> Signed-off-by: Emmanuel Deloget
>
> Index: toolchain/eglibc/Config.in
> =
On 04/18/2012 11:17 PM, Peter Naulls wrote:
> Unless something has changed very recently, 2.12 and 2.14 builds have
> been broken for as long as I've been looking at them, which is the
> best part of a year. Only 2.13 builds, and even then you still
> need some additional e/glibc patches for the
On 04/19/2012 11:43 AM, Emmanuel Deloget wrote:
> Checked with 2.13, and it indeed works.
Glad to hear!
> Regarding eglibc selection, it feels weird to me to be able to select
> both a version AND a revision. If I want version 2.12, I will probably
> stick to its corresponding revision. Same for
I see that a number of targets were recently bumped up to kernel 3.2.15,
including the x86 subtargets like the alix and geos. However, the
generic x86 target remains on 2.6.39:
adam@openwrt-builder:~/Desktop/openwrt/trunk$ cat target/linux/x86/Makefile
#
# Copyright (C) 2006-2011 OpenWrt.org
#
Le 18/04/2012 23:17, Peter Naulls a écrit :
On 04/17/2012 11:15 AM, Mirko Vogt wrote:
Hey Emmanuel,
I levelled up all versions of eglibc to i's latest revisions of its
respective branches ( https://dev.openwrt.org/changeset/31300 ) and
therewith I guess broke eglibc version 2.12 which I'd like
Hi,
Currently in see this in ./package/kernel/Makefile:
SCAN_DEPS=modules/*.mk
As a result, any modifications in target/linux/*/modules.mk wouldnt come
into effect for subsequent "make menuconfig" unless we delete ./tmp.
Would this be a correct solution?:
SCAN_DEPS=modules/*.mk $(TOPDIR)/target/
19 matches
Mail list logo
