Re: [OpenWrt-Devel] External toolchain cannot find -lgcc_s
On Monday 22 March 2010 01:54:28 Pawel Pastuszak wrote: Thanks for pointing me to the thread after reading the thread about Compiling outside of buildroot I was able to make and image. But now the problem that i am having is that the image is not booting the ramdisk which is an ext2 its compile about /etc/preinit fail but when i uses my older ramdisk image very thing is good. Any Ideas? Check that your kernel has support for initrd and ext2 filesystem, that should do it. Also check that you correctly set the initrd start address and size. On Mon, Mar 15, 2010 at 5:05 AM, Bas Mevissen ab...@basmevissen.nl wrote: On Sat, 2010-03-13 at 22:22 -0500, Pawel Pastuszak wrote: Hi All, I am trying to split the toolchain out of my main openwrt build, after generating the toolchain i moved it to a new location from staging_dir/toolchain-powerpc_gcc-4.3.3_glibc-2.7 and set up and new build that points to the toolchain. I am using Revision: 20023. Is there any think that I am missing? powerpc-openwrt-linux-gnu-gcc -Os -pipe -funit-at-a-time -mcpu=405 -msoft-float -Wall -Wunused -I./include/linux/include/ -Iinclude/ -DARPTABLES_VERSION=\0.0.3-3\ -o arptables arptables-standalone.o arptables.o libarptc/libarptc.o extensions/arpt_standard.o extensions/arpt_mangle.o /development/external_toolchain_test/usr/bin/../lib/gcc/powerpc-openwrt- linux-gnu/4.3.3/../../../../powerpc-openwrt-linux-gnu/bin/ld: cannot find -lgcc_s collect2: ld returned 1 exit status make[4]: *** [arptables] Error 1 make[4]: Leaving directory `/development/openwrt/build_dir/target-powerpc-openwrt-linux-gnu/arptabl es-v0.0.3-3' make[3]: *** [/development/openwrt/build_dir/target-powerpc-openwrt-linux-gnu/arptabl es-v0.0.3-3/.built] Error 2 make[3]: Leaving directory `/development/openwrt/package/arptables' make[2]: *** [package/arptables/compile] Error 2 make[2]: Leaving directory `/development/openwrt' Looks like a relocation problem. In general, gcc has a hard coded absolute path to some libraries. Solution is to compile the cross compiler for your new destination path or fix the binary. This has been discussed quite recently here in the Compiling outside of buildroot thread. Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC] support for new board WBD222
Hi, did anybody review it? Any comments? If not, maybe merge it to main line? Darius. On 03/17/2010 11:39 AM, Darius Augulis wrote: Hi all, we have developed new board WBD222. It is very similar to WBD111 and is based on SL3512 CPU. New board has two ethernet interfaces, two mini-PCI, one SATA, one mini-PCIe and two USB 2.0 interfaces. At the moment we have only few prototypes. Below is attached patch to add support for this board to OpenWRT. All comments are appreciated. Darius A. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Fix package/Makefile
Le Sat, 20 Mar 2010 12:20:50 +0100, Florian Fainelli flor...@openwrt.org a écrit : Hi Raphaël, Le vendredi 5 mars 2010 17:37:15, Raphaël HUCK a écrit : Hi, this patch fixes package/Makefile. You add /usr/lib/ebtables, should not you also add /usr/lib/iptables? Hi Florian, yes it's a good idea to add /usr/lib/iptables too :) -Raphael ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] AR7240 switch // was: TP-Link TL-WR741ND: broadcasts on ethernet not reaching CPU
On Fri, 2010-03-19 at 16:56 +0100, Joerg Albert wrote: I looked closer at the PCB and it turned out that we have a voltage divider with two 5.6 kOhm to V_3_3 and GND (R613, R614) and a capacitor C496 (!) towards the CPU. The signal at the CPU looked fine for a 2.5V TTL. The voltage drift seen above is probably caused by the capacitor unloading when the CPU pin is driven down. Curious design choice. Works fine for continuous signals at higher frequencies, but not here. I removed the resitors and replaced C496 by a 1k resistor (to protect the CPU pin against shorts). This solved my problem. I guess the above schematics was meant to be a cheap TTL level conversion 2.5V - 3.3V. Thanks for sending me again to the oscilloscope! I'm happy it is solved now. Maybe you can document this in relevant places on the web. Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mjpg-streamer and kernel crash again
On Fri, 2010-03-19 at 22:37 +0100, Kövesdi György wrote: Hi, At last i could create symbolic backtrace (attached). The hardware is an Asus WL500GP-V2, a 160 Gb HD (on USB), a UVC webcam (Logitech Quickcam Sphere). The commandline is: mjpg-streamer -i input_uvc.so -f 25 -r 320x240 -l off -o output_file.so -r /data/jpeg 128Mb swap is used. Some commands are executed immediately before crash (see the attached file), the free memory and other things are shown. I cannot imagine that all the memory got allocated within some seconds (filling 128Mb space through USB takes some time). I assume that there is a problem in the kernel instead. Where is the output of mjpg-streamer written to? It looks like it is using ram disk or (slow) flash memory. Make sure it is on the hard disk. What is the rate of data being written? If, for some reason, the disk (flash?) is too slow, you run out of memory due to the block layer buffering. You can measure the USB disk performance by copying a piece of dat from e.g. /dev/zero to the disk with dd. Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] openntpd resists arrest
So please do not hesitate to submit patches in the future, it should be quite a bit more pleasurable than it may have been previously. Definitely. I wasn't so much complaining as rejoicing at the fact that patch submission seems to be working now. As Emacs maintainer, I know full well that it's tremendously difficult to give the needed attention to every submission, so when a patch of mine gets ignored, I do get frustrated of course but I also know the other side is equally frustrated at not being able to keep up. Stefan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mjpg-streamer and kernel crash again
Where is the output of mjpg-streamer written to? It looks like it is
using ram disk or (slow) flash memory. Make sure it is on the hard disk.
Sorry, i forgot to mention that there is a link:
/data - /mnt/xxx/
which point to the HD.
What is the rate of data being written? If, for some reason, the disk
(flash?) is too slow, you run out of memory due to the block layer
buffering.
The measured maximum recorded rate is ~23 fps. My very first try was recording
one picture in every 15 second, which is very slow, and it also leaded to
crash in 3 days. Faster recording crashes sooner.
--
I checked some out-of-memory situations, and found strange things. You can
easily try it (i would like to hear if it works on your system or not): create
a big directory (~50k...100k files) and give a simple 'ls' command:
$ ls /my/big/directory
No swap is in use, my physical memory is 32M.
The 'ls' allocates very much memory, which leads to out-of-memory. AFAIK, the
kernel calls the oom-killer, which should kill the biggest process ('ls' in
this case). It happens, but the system hangs. Some seconds later the following
message appears on the console:
bcm47xx_wdtWatchdog will fire soon!!!
This is the very last message, the system does not respond any more.
I think this situation should be handled correctly.
Thanx
K. Gy.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mjpg-streamer and kernel crash again
On Mon, 2010-03-22 at 15:30 +0100, Kövesdi György wrote:
Where is the output of mjpg-streamer written to? It looks like it is
using ram disk or (slow) flash memory. Make sure it is on the hard disk.
Sorry, i forgot to mention that there is a link:
/data - /mnt/xxx/
which point to the HD.
OK, wanted to be sure that we are hunting a real bug. Did you check that
the files are actually written to that disk?
What is the rate of data being written? If, for some reason, the disk
(flash?) is too slow, you run out of memory due to the block layer
buffering.
The measured maximum recorded rate is ~23 fps. My very first try was
recording
one picture in every 15 second, which is very slow, and it also leaded to
crash in 3 days. Faster recording crashes sooner.
Sounds like a memory leak of the application. Or some (debug) log asking
too much memory. Maybe /var/log/messages is getting huge?
--
I checked some out-of-memory situations, and found strange things. You can
easily try it (i would like to hear if it works on your system or not):
create
a big directory (~50k...100k files) and give a simple 'ls' command:
$ ls /my/big/directory
No swap is in use, my physical memory is 32M.
The 'ls' allocates very much memory, which leads to out-of-memory. AFAIK, the
kernel calls the oom-killer, which should kill the biggest process ('ls' in
this case).
I'm not sure that it kills the biggest process first.
It happens, but the system hangs. Some seconds later the following
message appears on the console:
bcm47xx_wdtWatchdog will fire soon!!!
This is the very last message, the system does not respond any more.
I think this situation should be handled correctly.
What keeps the watchdog happy? It that still alive after the OOM-killer?
Bas.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] Add yaddns package
Hi, this patch adds a package for yaddns: http://sourceforge.net/projects/yaddns/ Yaddns is a small ddns client with multiple ddns server supports (dyndns, ...) and a high flexibility. Yaddns is particularly appropriate for embedded systems. -Raphaeldiff -pruN net.orig/yaddns/Makefile net/yaddns/Makefile --- net.orig/yaddns/Makefile 1970-01-01 01:00:00.0 +0100 +++ net/yaddns/Makefile 2010-03-22 16:35:14.0 +0100 @@ -0,0 +1,40 @@ +# +# Copyright (C) 2006-2010 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +include $(TOPDIR)/rules.mk + +PKG_NAME:=yaddns +PKG_VERSION:=0.1.1 +PKG_RELEASE:=1 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 +PKG_SOURCE_URL:=...@sf/yaddns +PKG_MD5SUM:=2708d3e47a486b1872ef9c5537cd2f0d + +PKG_INSTALL:=1 + +include $(INCLUDE_DIR)/package.mk + +define Package/yaddns + SECTION:=net + CATEGORY:=Network + DEPENDS:= + TITLE:=Yet Another DDNS client + URL:=http://patatrac.info/yaddns +endef + +define Package/yaddns/description +Yaddns is a small ddns client with multiple ddns server supports (dyndns, ...) +and a high flexibility. Yaddns is particularly appropriate for embedded systems. +endef + +define Package/yaddns/install + $(INSTALL_DIR) $(1)/usr/bin + $(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/bin/yaddns $(1)/usr/bin/ +endef + +$(eval $(call BuildPackage,yaddns)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Howto debug init scripts like preinit?
I've never needed to really get into the startup scripts much but now I need to try and understand how the mini_fo union gets set up so I'm trying to learn the startup scripts like preinit. When I ad to fiddle with this part of the code, I'd add some echo blabla /tmp/mydebug in those scripts and then read the /tmp/mydebug file (of course, this only worked in those cases where the boot script did end up setting up my router in such a way that I was able to log in to look at the damn file). Another option might be to send that debug output to the network as is done in preinit_net_echo and read it via tcpdump. Stefan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] Add libowfat package
My first patch to openwrt, so I hope I got everything right. It adds libowfat (http://www.fefe.de/libowfat/) to OpenWRT and closes therefore (if accepted) https://dev.openwrt.org/ticket/6908. Libowfat is a library that implements various C APIs suggested by D.J. Bernstein. Also see http://cr.yp.to/software.html. Signed-off-by: Oliver Ripka olliwo...@gmail.com --- Index: libs/libowfat/Makefile === --- libs/libowfat/Makefile (revision 0) +++ libs/libowfat/Makefile (revision 0) @@ -0,0 +1,60 @@ +# +# Copyright (C) 2008 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id$ + +include $(TOPDIR)/rules.mk + +LOWFAT_VERSION=0.28 + +PKG_NAME:=libowfat +PKG_VERSION:=$(LOWFAT_VERSION) +PKG_RELEASE:=1 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 +PKG_SOURCE_URL:=http://dl.fefe.de +PKG_MD5SUM:=6bbee9a86506419657d87123b7a6f2c1 + +include $(INCLUDE_DIR)/package.mk + +# set to 1 to enable debugging +DEBUG= + +define Package/libowfat + SECTION:=libs + CATEGORY:=Libraries + TITLE:=reimplemented libdjb under GPL +endef + +define Build/Configure +endef + +TARGET_CFLAGS += $(FPIC) +LOWFAT_MAKEOPTS = \ + $(TARGET_CONFIGURE_OPTS) \ + COPTS=$(TARGET_CFLAGS) \ + DEBUG=$(DEBUG) \ + VERSION=$(LOWFAT_VERSION) \ + CPPFLAGS=-I$(PKG_BUILD_DIR) -I$(STAGING_DIR)/usr/include \ + OS=Linux + +# work around a nasty gcc bug +ifneq ($(CONFIG_GCC_VERSION_4_2_4),) + LOWFAT_MAKEOPTS += WOPTS= +endif + +define Build/Compile + $(MAKE) -C $(PKG_BUILD_DIR) $(LOWFAT_MAKEOPTS) +endef + +define Build/InstallDev + mkdir -p $(1)/usr/include/libowfat + $(CP) $(PKG_BUILD_DIR)/*.h $(1)/usr/include/libowfat + $(INSTALL_DIR) $(1)/usr/lib + $(CP) $(PKG_BUILD_DIR)/*.a $(1)/usr/lib +endef + +$(eval $(call BuildPackage,libowfat)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] External toolchain cannot find -lgcc_s
I would have to say that my address are setup correctly why would move the toolchain out of the my build would change the Ramdisk? This is the follow steps i took to see what was wrong Note: External Toolchain is the openwrt toolchain moved outside. 1) Using External Toolchain, make kernel and ramdisk fail to boot ram disk 2) Using Internal Toolchain to build kernel and external ramdisk fail to boot 3) Using Internal Toolchain to build kernel and internal toolchain ramdisk , boots fine. So what would cause /etc/preinit to to boot? maybe busybox is being compiled wrong? On Mon, Mar 22, 2010 at 5:00 AM, Florian Fainelli flor...@openwrt.org wrote: On Monday 22 March 2010 01:54:28 Pawel Pastuszak wrote: Thanks for pointing me to the thread after reading the thread about Compiling outside of buildroot I was able to make and image. But now the problem that i am having is that the image is not booting the ramdisk which is an ext2 its compile about /etc/preinit fail but when i uses my older ramdisk image very thing is good. Any Ideas? Check that your kernel has support for initrd and ext2 filesystem, that should do it. Also check that you correctly set the initrd start address and size. On Mon, Mar 15, 2010 at 5:05 AM, Bas Mevissen ab...@basmevissen.nl wrote: On Sat, 2010-03-13 at 22:22 -0500, Pawel Pastuszak wrote: Hi All, I am trying to split the toolchain out of my main openwrt build, after generating the toolchain i moved it to a new location from staging_dir/toolchain-powerpc_gcc-4.3.3_glibc-2.7 and set up and new build that points to the toolchain. I am using Revision: 20023. Is there any think that I am missing? powerpc-openwrt-linux-gnu-gcc -Os -pipe -funit-at-a-time -mcpu=405 -msoft-float -Wall -Wunused -I./include/linux/include/ -Iinclude/ -DARPTABLES_VERSION=\0.0.3-3\ -o arptables arptables-standalone.o arptables.o libarptc/libarptc.o extensions/arpt_standard.o extensions/arpt_mangle.o /development/external_toolchain_test/usr/bin/../lib/gcc/powerpc-openwrt- linux-gnu/4.3.3/../../../../powerpc-openwrt-linux-gnu/bin/ld: cannot find -lgcc_s collect2: ld returned 1 exit status make[4]: *** [arptables] Error 1 make[4]: Leaving directory `/development/openwrt/build_dir/target-powerpc-openwrt-linux-gnu/arptabl es-v0.0.3-3' make[3]: *** [/development/openwrt/build_dir/target-powerpc-openwrt-linux-gnu/arptabl es-v0.0.3-3/.built] Error 2 make[3]: Leaving directory `/development/openwrt/package/arptables' make[2]: *** [package/arptables/compile] Error 2 make[2]: Leaving directory `/development/openwrt' Looks like a relocation problem. In general, gcc has a hard coded absolute path to some libraries. Solution is to compile the cross compiler for your new destination path or fix the binary. This has been discussed quite recently here in the Compiling outside of buildroot thread. Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Sat, Mar 20, 2010 at 01:38:58PM +0100, Matthias Buecher / Germany wrote: Is the script set to executable (+x) in the image? This is typical for scripts that are presebt but not running, and often overlooked. Scripts in /lib/firstboot are not executable as they are sourced and not executed directly so that's not the problem here. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Sat, Mar 20, 2010 at 06:14:08PM +0100, Jo-Philipp Wich wrote: I think the real issue is that the preinit hook used by the fix script is not executed on jffs2-only images. Exactly, this script is added to the switch2jffs hooks which aren't executed on a pure jffs2 image. It seems there are just 2 hooks: switch2jffs and jffs2reset, neither seems appropiate for this kind of scripts. It would be nice to have another independent of filesystems hook but I'm not a preinit expert as it seems to me a little overcomplicated, hopefully someone who knows can give the OP advice as his fix is necesary. Thank you! - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Serial port question - Atheros
Hi, On a Meraki mini, Atheros ar2315 SOC I am trying take over the serial port as in: minicom -s [/dev/ttyS0]. Lock file gets made OK. I notice there are MANY serial port related entries in System.map (serial, tty, uart, etc.) And several /dev entries. I have yet to figure out what to do so minicom can talk over the SOC serial port??!! It ought to be simple ;-). Has anyone found a simple way to do this? Thanks, Wiz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Serial port question - Atheros
You probably need to comment out the console entries for the serial port(s) in /etc/inittab and then try again. That should free up the port for use with minicom (or any other serial app). You have to reboot to have the change take effect, unless you customize your busybox (compile your own image) to allow a kill signal to force an inittab reload. Also, of course, doing this disables the serial console completely (after boot messages, no shell), so don't biff your networking setup or you'll be forced to reflash. On Mon, 2010-03-22 at 16:47 -0500, RHS Linux User wrote: Hi, On a Meraki mini, Atheros ar2315 SOC I am trying take over the serial port as in: minicom -s [/dev/ttyS0]. Lock file gets made OK. I notice there are MANY serial port related entries in System.map (serial, tty, uart, etc.) And several /dev entries. I have yet to figure out what to do so minicom can talk over the SOC serial port??!! It ought to be simple ;-). Has anyone found a simple way to do this? Thanks, Wiz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] External toolchain cannot find -lgcc_s
Hi Nico,
I compered the lib's between the two images and the both match, I am
still run different theories of mine why it couldn't boot. for now
here is my config settings
Is there any guide on what need to happen when complie using and
external toolchain?
CONFIG_TARGET_NAME=powerpc-openwrt-linux-gnu
CONFIG_TOOLCHAIN_PREFIX=powerpc-openwrt-linux-gnu-
CONFIG_TOOLCHAIN_ROOT=/opt/openwrt/OpenWrt-Toolchain-ems-for-powerpc-gcc-4.3.3_glibc-2.7/toolchain-powerpc_gcc-4.3.3_glibc-2.7
CONFIG_TOOLCHAIN_BIN_PATH=./usr/bin ./bin
CONFIG_TOOLCHAIN_INC_PATH=./usr/include ./include
CONFIG_TOOLCHAIN_LIB_PATH=./usr/lib ./lib
# CONFIG_EXTRA_TARGET_ARCH is not set
#
# Configuration
#
CONFIG_LIBC_ROOT_DIR=/opt/openwrt/OpenWrt-Toolchain-ems-for-powerpc-gcc-4.3.3_glibc-2.7/toolchain-powerpc_gcc-4.3.3_glibc-2.7
CONFIG_LIBC_FILE_SPEC=./lib/ld{*.so,-linux*.so.*}
./lib/lib{anl,c,cidn,crypt,dl,m,nsl,nss_dns,nss_files,resolv,util}{-*.so,.so.*}
CONFIG_PACKAGE_libgcc=y
#
# Configuration
#
CONFIG_LIBGCC_ROOT_DIR=/opt/openwrt/OpenWrt-Toolchain-ems-for-powerpc-gcc-4.3.3_glibc-2.7/toolchain-powerpc_gcc-4.3.3_glibc-2.7
CONFIG_LIBGCC_FILE_SPEC=./lib/libgcc_s.so.*
CONFIG_PACKAGE_libpthread=y
#
# Configuration
#
CONFIG_LIBPTHREAD_ROOT_DIR=/opt/openwrt/OpenWrt-Toolchain-ems-for-powerpc-gcc-4.3.3_glibc-2.7/toolchain-powerpc_gcc-4.3.3_glibc-2.7
CONFIG_LIBPTHREAD_FILE_SPEC=./lib/libpthread{-*.so,.so.*}
CONFIG_PACKAGE_librt=y
#
# Configuration
#
CONFIG_LIBRT_ROOT_DIR=/opt/openwrt/OpenWrt-Toolchain-ems-for-powerpc-gcc-4.3.3_glibc-2.7/toolchain-powerpc_gcc-4.3.3_glibc-2.7
CONFIG_LIBRT_FILE_SPEC=./lib/librt{-*.so,.so.*}
CONFIG_PACKAGE_libstdcpp=y
#
# Configuration
#
CONFIG_LIBSTDCPP_ROOT_DIR=/opt/openwrt/OpenWrt-Toolchain-ems-for-powerpc-gcc-4.3.3_glibc-2.7/toolchain-powerpc_gcc-4.3.3_glibc-2.7
CONFIG_LIBSTDCPP_FILE_SPEC=./usr/lib/libstdc++.so
./usr/lib/libstdc++.so.6.0.10 ./usr/lib/libstdc++.so.6
CONFIG_LDCONFIG_ROOT_DIR=/opt/openwrt/OpenWrt-Toolchain-ems-for-powerpc-gcc-4.3.3_glibc-2.7/toolchain-powerpc_gcc-4.3.3_glibc-2.7
CONFIG_LDCONFIG_FILE_SPEC=./sbin/ldconfig
Thanks,
Pawel
On Mon, Mar 22, 2010 at 3:33 PM, Nico n...@openwrt.org wrote:
Hi Pawel,
Did you check that all libraries required to boot the system are present ?
When using an external toolchain, you have to tell the build system
where the base libraries (libc, libgcc, libpthread...) are to be found,
check your .config file. You can also check in
build_dir/target-*/root-* that all files have been properly installed
before the ramdisk image was generated.
Let us know what's going on...
Cheers,
--
-{Nico}
Pawel Pastuszak wrote:
I would have to say that my address are setup correctly why would move
the toolchain out of the my build would change the Ramdisk?
This is the follow steps i took to see what was wrong
Note: External Toolchain is the openwrt toolchain moved outside.
1) Using External Toolchain, make kernel and ramdisk fail to boot ram disk
2) Using Internal Toolchain to build kernel and external ramdisk fail to boot
3) Using Internal Toolchain to build kernel and internal toolchain
ramdisk , boots fine.
So what would cause /etc/preinit to to boot? maybe busybox is being
compiled wrong?
On Mon, Mar 22, 2010 at 5:00 AM, Florian Fainelli flor...@openwrt.org
wrote:
On Monday 22 March 2010 01:54:28 Pawel Pastuszak wrote:
Thanks for pointing me to the thread after reading the thread about
Compiling outside of buildroot I was able to make and image.
But now the problem that i am having is that the image is not booting
the ramdisk which is an ext2 its compile about /etc/preinit fail but
when i uses my older ramdisk image very thing is good. Any Ideas?
Check that your kernel has support for initrd and ext2 filesystem, that
should
do it. Also check that you correctly set the initrd start address and size.
On Mon, Mar 15, 2010 at 5:05 AM, Bas Mevissen ab...@basmevissen.nl wrote:
On Sat, 2010-03-13 at 22:22 -0500, Pawel Pastuszak wrote:
Hi All,
I am trying to split the toolchain out of my main openwrt build, after
generating the toolchain i moved it to a new location from
staging_dir/toolchain-powerpc_gcc-4.3.3_glibc-2.7 and set up and new
build that points to the toolchain.
I am using Revision: 20023.
Is there any think that I am missing?
powerpc-openwrt-linux-gnu-gcc -Os -pipe -funit-at-a-time -mcpu=405
-msoft-float -Wall -Wunused -I./include/linux/include/ -Iinclude/
-DARPTABLES_VERSION=\0.0.3-3\ -o arptables arptables-standalone.o
arptables.o libarptc/libarptc.o extensions/arpt_standard.o
extensions/arpt_mangle.o
/development/external_toolchain_test/usr/bin/../lib/gcc/powerpc-openwrt-
linux-gnu/4.3.3/../../../../powerpc-openwrt-linux-gnu/bin/ld: cannot find
-lgcc_s
collect2: ld returned 1 exit status
make[4]: *** [arptables] Error 1
make[4]: Leaving directory
`/development/openwrt/build_dir/target-powerpc-openwrt-linux-gnu/arptabl
es-v0.0.3-3' make[3]: ***
Re: [OpenWrt-Devel] [PATCH] Add libowfat package
Added r20376, next time a patch attached to a ticket will suffice. Travis On Mon, Mar 22, 2010 at 1:24 PM, Oliver Ripka olliwo...@gmail.com wrote: My first patch to openwrt, so I hope I got everything right. It adds libowfat (http://www.fefe.de/libowfat/) to OpenWRT and closes therefore (if accepted) https://dev.openwrt.org/ticket/6908. Libowfat is a library that implements various C APIs suggested by D.J. Bernstein. Also see http://cr.yp.to/software.html. Signed-off-by: Oliver Ripka olliwo...@gmail.com --- Index: libs/libowfat/Makefile === --- libs/libowfat/Makefile (revision 0) +++ libs/libowfat/Makefile (revision 0) @@ -0,0 +1,60 @@ +# +# Copyright (C) 2008 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id$ + +include $(TOPDIR)/rules.mk + +LOWFAT_VERSION=0.28 + +PKG_NAME:=libowfat +PKG_VERSION:=$(LOWFAT_VERSION) +PKG_RELEASE:=1 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 +PKG_SOURCE_URL:=http://dl.fefe.de +PKG_MD5SUM:=6bbee9a86506419657d87123b7a6f2c1 + +include $(INCLUDE_DIR)/package.mk + +# set to 1 to enable debugging +DEBUG= + +define Package/libowfat + SECTION:=libs + CATEGORY:=Libraries + TITLE:=reimplemented libdjb under GPL +endef + +define Build/Configure +endef + +TARGET_CFLAGS += $(FPIC) +LOWFAT_MAKEOPTS = \ + $(TARGET_CONFIGURE_OPTS) \ + COPTS=$(TARGET_CFLAGS) \ + DEBUG=$(DEBUG) \ + VERSION=$(LOWFAT_VERSION) \ + CPPFLAGS=-I$(PKG_BUILD_DIR) -I$(STAGING_DIR)/usr/include \ + OS=Linux + +# work around a nasty gcc bug +ifneq ($(CONFIG_GCC_VERSION_4_2_4),) + LOWFAT_MAKEOPTS += WOPTS= +endif + +define Build/Compile + $(MAKE) -C $(PKG_BUILD_DIR) $(LOWFAT_MAKEOPTS) +endef + +define Build/InstallDev + mkdir -p $(1)/usr/include/libowfat + $(CP) $(PKG_BUILD_DIR)/*.h $(1)/usr/include/libowfat + $(INSTALL_DIR) $(1)/usr/lib + $(CP) $(PKG_BUILD_DIR)/*.a $(1)/usr/lib +endef + +$(eval $(call BuildPackage,libowfat)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] disable ipk stripping
Hello, I am trying to compile the clamav package for kamikaze x86. The compile process is stripping the binaries - rstrip.sh: /home/vsawant/Documents/projects/routers/openwrtsrc/build_dir/target-i386_uClibc-0.9.30.1/clamav-0.95.3/ipkg-x86/clamav/usr/sbin/clamscan:executable. How to disable the strip to debug the binaries using gdb? Thanks, Vipul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] disable ipk stripping
Hi Vipul,
There is a Binary stripping method option under Global build
settings where you can choose how binaries should be stripped (or not).
Cheers,
--
-{Nico}
On 23/03/10 03:59, Vipul M Sawant wrote:
Hello,
I am trying to compile the clamav package for kamikaze x86. The
compile process is stripping the binaries - rstrip.sh:
/home/vsawant/Documents/projects/routers/openwrtsrc/build_dir/target-i386_uClibc-0.9.30.1/clamav-0.95.3/ipkg-x86/clamav/usr/sbin/clamscan:executable.
How to disable the strip to debug the binaries using gdb?
Thanks,
Vipul
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] disable ipk stripping
Hi Nico,
Yes, it worked :). Thanks a lot.
- Vipul
On Tue, Mar 23, 2010 at 8:34 AM, Nico n...@openwrt.org wrote:
Hi Vipul,
There is a Binary stripping method option under Global build
settings where you can choose how binaries should be stripped (or not).
Cheers,
--
-{Nico}
On 23/03/10 03:59, Vipul M Sawant wrote:
Hello,
I am trying to compile the clamav package for kamikaze x86. The
compile process is stripping the binaries - rstrip.sh:
/home/vsawant/Documents/projects/routers/openwrtsrc/build_dir/target-i386_uClibc-0.9.30.1/clamav-0.95.3/ipkg-x86/clamav/usr/sbin/clamscan:executable.
How to disable the strip to debug the binaries using gdb?
Thanks,
Vipul
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Howto debug init scripts like preinit?
On Sun, 2010-03-21 at 20:41 -0400, Brian Hutchinson wrote: Hi, I've never needed to really get into the startup scripts much but now I need to try and understand how the mini_fo union gets set up so I'm trying to learn the startup scripts like preinit. I'm using a Pronghorn SBC (ixp-42xx) and I thought that maybe if I edited preinit and put #!/bin/sh -x that I could turn on debugging and see what the scripts were doing via the serial console. That didn't work so well. How you all debug startup scripts? It depends on the error. If the problem is that preinit doesn't start at all, that usually indicates a syntax error or some such in the start up scripts, so on the host, I fire up dash, and do something like: for script in *; do . $script done in the build_dir/target.../root.../lib/preinit directory If there is a syntax error it will emit an error message and it can be fixed. Errors that prevent successful sourcing of files will cause preinit to die. I can't change preinit from the target can I? I tried but I guess it I was going to suggest using a 'pure' jffs image, but I realized that defeats the purpose of what you are trying to test. For a squashfs, the preinit runs from squashfs, not jffs (because mounting the jffs is part of the preinit functionality; probably the most important). isn't using the one from /jffs and is using the one from /rom. I had to rebuild the image to get my preinit changes to execute on startup. Stefan had good suggestions for the rest. -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore (Daniel Dickinson's Website) http://cshore.is-a-geek.com signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Howto debug init scripts like preinit?
On Mon, 2010-03-22 at 12:24 -0400, Stefan Monnier wrote: Another option might be to send that debug output to the network as is done in preinit_net_echo and read it via tcpdump. You can also use socat to receive the udp broadcasts without exiting after the first one. -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore (Daniel Dickinson's Website) http://cshore.is-a-geek.com signature.asc Description: This is a digitally signed message part ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
