Re: [leaf-devel] FW: compiling nut
hi, that did the trick !, nut compiles fine now. Thanks -Oorspronkelijk bericht- Van: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] Verzonden: za 6-11-2010 14:17 Aan: leaf-devel@lists.sourceforge.net Onderwerp: Re: [leaf-devel] FW: compiling nut Hi Stefaan, On Sat, 2010-11-06 at 10:51 +0100, Stefaan Van Dooren wrote: > checking for libusb version via pkg-config... checking via libusb-config... > 0.1.12 found > checking for libusb cflags... > checking for libusb ldflags... -L/usr/lib -lusb > checking for usb.h... yes > checking for usb_init... no This is the problem - it doesn't find usb_init() so it concludes that libusb isn't going to work The root cause is that it is looking for libusb.so in /usr/lib (on the build host), which is wrong... I have modified source/nut/buildtool.mk to add --with-usb-includes and --with-usb-libs for the "configure" command. It works for me now, but then it worked for me (and Andrew) before... Could you try again please. Should be sufficient to run: buildtool.pl srcclean nut rm -rf source/nut buildtool.pl build nut dMb -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] FW: compiling nut
I accidentallty answerd to David directly instead of the list. -Oorspronkelijk bericht- Van: Stefaan Van Dooren Verzonden: za 6-11-2010 10:29 Aan: davidMbrooke Onderwerp: RE: [leaf-devel] compiling nut The log is pasted below : buildtool::Make::Source::_makeEnvString:envstring= SOURCE=nut-2.4.3.tar.gz PATCH1=nut-uclibc.patch LANG=C checking link /lib/ld-uClibc.so make: Map '/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/nut' wordt binnengegaan (cd nut-2.4.3 ; CC=/home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 LD=/home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/usr/bin/ld \ CFLAGS="-Os -march=i486 -mtune=pentiumpro -g -Wall" LIBS="-lm" \ LIBC_INCLUDE=/home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/include \ KERNEL_INCLUDE=/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/linux/linux-/include \ ./configure --prefix=/usr \ --sysconfdir=/etc/nut \ --localstatedir=/var/run \ --with-usb \ --with-drivers=all \ ; cd drivers; BT_ST_DIR=/home/stefaan/leaf/src/bering-uclibc4/buildtool/staging sh ../../patch-mkfile) Network UPS Tools version 2.4.3 checking build system type... i386-pc-linux-gnu checking host system type... i386-pc-linux-gnu checking target system type... i386-pc-linux-gnu checking for host system name... ubuntu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 accepts -g... yes checking for /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 option to accept ISO C89... none needed checking dependency style of /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32... gcc3 checking how to run the C preprocessor... /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... (cached) /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 checking whether we are using the GNU C compiler... (cached) yes checking whether /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 accepts -g... (cached) yes checking for /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 option to accept ISO C89... (cached) none needed checking dependency style of /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32... (cached) gcc3 checking whether /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 and cc understand -c and -o together... yes checking how to run the C preprocessor... /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32 -E checking for egrep... (cached) /bin/grep -E checking for ar... /home/stefaan/leaf/src/bering-uclibc4/buildtool/staging/usr/bin/ar checking for ranlib... ranlib checking whether byte ordering is bigendian... no checking for inline... inline checking for flexible array members... yes checking for variable-length arrays... yes checking for flock... yes checking for lockf... yes checking for fcvt... no checking for fcvtl... no checking for cfsetispeed... yes checking for tcsendbreak... yes checking for seteuid... yes checking for setsid... yes checking for getpassphrase... no checking for on_exit... yes checking for strptime... yes checking for vsnprintf... yes checking for snprintf... yes checking for setenv... yes checking for inet_aton... yes checking for strerror... yes checking for atexit... yes checking whether optind is declared... yes checking whether uu_lock is declared... no checking whether __func__ is declared... yes checking for library containing gethostbyname... none required checking for library containing connect... none requir
Re: [leaf-devel] compiling nut
did you fix this issue ? I'm having the same problem. I allready tried to send the "config.log" from nut, but it didn't made it to the list. Stefaan -Oorspronkelijk bericht- Van: Andrew [mailto:ni...@seti.kr.ua] Verzonden: di 2-11-2010 23:03 Aan: leaf-devel@lists.sourceforge.net Onderwerp: Re: [leaf-devel] compiling nut 02.11.2010 23:53, KP Kirchdoerfer ?: > Hi; > > I've never been able to build the nut package... > > It fails with the message: > checking whether to build serial drivers... yes > checking whether to build SNMP drivers... no > configure: error: "USB drivers requested, but libusb not found." > sed: can't read Makefile: No such file or directory > > any hints? > > kp Hm, strange, for me all is ok: checking whether to build serial drivers... yes checking whether to build SNMP drivers... yes checking whether to build USB drivers... yes checking whether to enable HAL support... no checking whether to build neon based XML driver... no Can you send me config.log from nut and full buildenv log for nut building? -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Problem building buildenv [SOLVED]
Fixed it using this site : http://docwiki.gumstix.org/Buildroot Makeinfo on my system was version 4.13 2. Workaround version check bug. If you still get the error message above AND you're sure that makeinfo is properly installed on your path, then type makeinfo --version If your makeinfo version is 4.11 or higher, then you may have encountered a well-known `binutils' bug. In short, the build scripts incorrectly thinks 4.11 is an older version than 4.4. If you are sure that you have a correct version of makeinfo, then you can manually remove this broken check. In `gumstix-buildroot/toolchain_build_arm_nofpu/binutils-2.17.50.0.6-build/ Makefile', find: MAKEINFO = /projects/eink/gumstix-buildroot/toolchain_build_arm_nofpu/binutils-2.17 .50.0.6/missing makeinfo and change it to MAKEINFO = /usr/bin/makeinfo See this thread for others ways to work around this bug, including a patch. > -Oorspronkelijk bericht----- > Van: Stefaan Van Dooren [mailto:stef...@3-c.be] > Verzonden: woensdag 3 november 2010 11:16 > Aan: leaf-devel@lists.sourceforge.net > Onderwerp: [leaf-devel] Problem building buildenv > > Seeing the progress being made on version 4, I decided to > give it another go myself. But I'm having problems building > the buildenv. (I have done it before with success) > > This is a clean checkout.(fresh start) The error below is > after the second time I tried it, so not all "OK" messages > are there anymore. > > Makeinfo is installed (Ubuntu 10.04 LTS) > > > stef...@ubuntu:~/leaf/src/bering-uclibc4/buildtool$ ./buildtool.pl build buildenv make the list of required source > packages: nothing to do [0.K.] make the list of required > build packages: buildenv [0.K.] > > build source/package: buildenv > > calling 'make build' for buildenv make build failed for > /home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builden v/buildtoo > l.mk , please have a look at the logfile log/buildtoollog at > buildtool/Make/Source.pm line 398. > stef...@ubuntu:~/leaf/src/bering-uclibc4/buildtool$ > > > And the logfile : > > > make[3]: Leaving directory > `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builde nv/binutil > s-2.20.1-build/intl' > make[3]: Entering directory > `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builde nv/binutil > s-2.20.1-build/bfd' > Making info in doc > make[4]: Entering directory > `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builde nv/binutil > s-2.20.1-build/bfd/doc' > restore=: && backupdir=".am$$" && \ > rm -rf $backupdir && mkdir $backupdir && \ > if > (/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builde nv/binutil > s-2.20.1/missing makeinfo --split-size=500 --split-size=500 > --version) >/dev/null 2>&1; then \ > for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] > bfd.i[0-9] bfd.i[0-9][0-9]; do \ > if test -f $f; then mv $f $backupdir; restore=mv; > else :; fi; \ > done; \ > else :; fi && \ > if > /home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builden v/binutils > -2.20.1/missing makeinfo --split-size=500 > --split-size=500 -I > /home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builden v/binutils > -2.20.1/bfd/doc \ >-o bfd.info `test -f 'bfd.texinfo' || echo > '/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builde nv/binutil > s-2.20.1/bfd/doc/'`bfd.texinfo; \ > then \ > rc=0; \ > else \ > rc=$?; \ > $restore $backupdir/* `echo "./bfd.info" | sed > 's|[^/]*$||'`; \ > fi; \ > rm -rf $backupdir; exit $rc > WARNING: `makeinfo' is missing on your system. You should > only need it if > you modified a `.texi' or `.texinfo' file, or any other file > indirectly affecting the aspect of the manual. The spurious > call might also be the consequence of using a buggy `make' > (AIX, > DU, IRIX). You might want to install the `Texinfo' > package or > the `GNU make' package. Grab either from any GNU > archive site. > make[4]: *** [bfd.info] Error 1 > make[4]: Leaving directory > `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builde nv/binutil > s-2.20.1-build/bfd/doc' > Making info in po > make[4]: Entering directory > `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/builde nv/binutil > s-2.20.1-build/bfd/po' > make[4]: Nothing to be done for `info'. > make[4]: Leaving directory > `/home/stefaan/leaf/src/bering-uclibc4/
[leaf-devel] Problem building buildenv
Seeing the progress being made on version 4, I decided to give it another go myself. But I'm having problems building the buildenv. (I have done it before with success) This is a clean checkout.(fresh start) The error below is after the second time I tried it, so not all "OK" messages are there anymore. Makeinfo is installed (Ubuntu 10.04 LTS) stef...@ubuntu:~/leaf/src/bering-uclibc4/buildtool$ ./buildtool.pl build buildenv make the list of required source packages: nothing to do [0.K.] make the list of required build packages: buildenv [0.K.] build source/package: buildenv calling 'make build' for buildenv make build failed for /home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/buildtoo l.mk , please have a look at the logfile log/buildtoollog at buildtool/Make/Source.pm line 398. stef...@ubuntu:~/leaf/src/bering-uclibc4/buildtool$ And the logfile : make[3]: Leaving directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/intl' make[3]: Entering directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/bfd' Making info in doc make[4]: Entering directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/bfd/doc' restore=: && backupdir=".am$$" && \ rm -rf $backupdir && mkdir $backupdir && \ if (/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1/missing makeinfo --split-size=500 --split-size=500 --version) >/dev/null 2>&1; then \ for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] bfd.i[0-9][0-9]; do \ if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \ done; \ else :; fi && \ if /home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutils -2.20.1/missing makeinfo --split-size=500 --split-size=500 -I /home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutils -2.20.1/bfd/doc \ -o bfd.info `test -f 'bfd.texinfo' || echo '/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1/bfd/doc/'`bfd.texinfo; \ then \ rc=0; \ else \ rc=$?; \ $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \ fi; \ rm -rf $backupdir; exit $rc WARNING: `makeinfo' is missing on your system. You should only need it if you modified a `.texi' or `.texinfo' file, or any other file indirectly affecting the aspect of the manual. The spurious call might also be the consequence of using a buggy `make' (AIX, DU, IRIX). You might want to install the `Texinfo' package or the `GNU make' package. Grab either from any GNU archive site. make[4]: *** [bfd.info] Error 1 make[4]: Leaving directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/bfd/doc' Making info in po make[4]: Entering directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/bfd/po' make[4]: Nothing to be done for `info'. make[4]: Leaving directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/bfd/po' make[4]: Entering directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/bfd' make[4]: Nothing to be done for `info-am'. make[4]: Leaving directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/bfd' make[3]: *** [info-recursive] Error 1 make[3]: Leaving directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/bfd' make[2]: *** [all-bfd] Error 2 make[2]: Leaving directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build' make: *** [/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv/binutil s-2.20.1-build/binutils/objdump] Fout 2 make: Map '/home/stefaan/leaf/src/bering-uclibc4/buildtool/source/buildenv' wordt verlaten -- Achieve Improved Network Security with IP and DNS Reputation. Defend against bad network traffic, including botnets, malware, phishing sites, and compromised hosts - saving your company time, money, and embarrassment. Learn More! http://p.sf.net/sfu/hpdev2dev-nov ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] General newbie remarks
Hi,
I'm new to this list and leaf-development, but I'm using leaf since it still
was LRP. Normally I just use whatever is available in the iso-image.
Recently I needed a special kernel (with siimage support compiled in), so I
decided to give buildtool for ucBering a chance.
I installed Config::General as noted in the docs, used cvs to get buildtool,
and then tried to build the environment.
It complained about "&main::ParseConfig", after awhile I figured that
replacing "ParseConfig" by "Config::General::ParseConfig" in buildtool.pl
and in "buildtool/Make/Source.pm" solved that problem.
Question : Is this a known problem or a problem with my distro ? I'm using a
fresh slackware 11 install in vmware to build everything.
Now that I can compile my own kernels, I decided to go a bit further and
rebuild the packages.
So I did :
./buildtool.pl pkglist | ./buildtool.pl build
Which stopped at building irmp3, giving an "syntax error near unexpected
token '(" error in it configure script.
Again after awhile, I figured that this was due to the fact that I'm using
bash as my standard shell. Changing the symbolic link for /bin/sh from bash
to zsh solved this problem.
Question : is this a known problem or a problem with the distro ?
Regards,
Stefaan
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [Leaf-devel] CF (write protect) + IDE adapter
A message I just received from Apacer Dear Stefaan, More information on the WP function. Apacer product is programmable for WP. The WP pin is low active, so WP wll be activated whenever the pin is asserted low. The system board, however, needs to have a WP controll logic to enable/disable WP. Not many M/B's supports such a control logic, so this is kind of a desgin-in feature. Partial WP by block is not supported by the current firmware version. It is technically feasible, but it depends on the quantity you required. Stefaan > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Noyes > Sent: vrijdag 8 februari 2002 1:40 > To: Matt Schalit; [EMAIL PROTECTED] > Subject: Re: [Leaf-devel] CF (write protect) + IDE adapter > > > > At 2002-02-07 14:12 -0800, Matt Schalit wrote: > >Stefaan Van Dooren wrote: > > > The three pin jumper is for master slave settings for IDE(at least > > > on the my modules it is). > > > > > > I don't see anything about writeprotect on the module. > > > > > > I will check the manuals asap. > > > >Perhaps you have different modules. The one refered to in > >the pdf file clearly shows a jumper on the module in Figure > >2-1 on the bottom of page 8: > > Matt, > This is where I got confused too. There is only one on-board jumper and > it's for selecting master/slave not WP#. Note 2 on the bottom of page 7 > mentions the on-board master/slave jumper. Figure 2-1 is apparently an > illustration of WP# implementation. There is no WP# jumper on the ADM. > > -- > Mike Noyes <[EMAIL PROTECTED]> > http://sourceforge.net/users/mhnoyes/ > http://leaf.sourceforge.net/content.php?menu=1000&page_id=4 > > > ___ > Leaf-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-devel > ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [Leaf-devel] CF (write protect) + IDE adapter
Mike, The three pin jumper is for master slave settings for IDE(at least on the my modules it is). I don't see anything about writeprotect on the module. I will check the manuals asap. Stefaan > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Noyes > Sent: donderdag 7 februari 2002 15:31 > To: Stefaan Van Dooren > Cc: [EMAIL PROTECTED] > Subject: RE: [Leaf-devel] CF (write protect) + IDE adapter > > > > At 2002-02-07 09:35 +0100, Stefaan Van Dooren wrote: > > > Apacer is making a ATA-Disk Module (ADM) too. > > > > > > http://www.apacer.com/product/flash/f_adc.htm > > > > > > >These are working great (have several of them running), but they > >don't have writeprotect switch, jumper. > > Stefaan, > This particular model does. Note: there is a three pin jumper at > the top of > the ATA-Disk Module, and the text below the image states: > > Extended Data Protection and Security > WP# pin for data protection > > If I'm wrong please correct me. Thanks. > > -- > Mike Noyes <[EMAIL PROTECTED]> > http://sourceforge.net/users/mhnoyes/ > http://leaf.sourceforge.net/content.php?menu=1000&page_id=4 > > > ___ > Leaf-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-devel > ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
RE: [Leaf-devel] CF (write protect) + IDE adapter
> Jeff, > Exactly. It's almost identical to the PQI DiskOnModule (DOM) product too. > I'm still trying to get pricing information. From what I can tell the > product came out in Oct, so the channel hasn't filled yet. Apacer > is making > a ATA-Disk Module (ADM) too. > > http://www.apacer.com/product/flash/f_adc.htm > These are working great (have several of them running), but they don't have writeprotect switch, jumper. Stefaan > -- > Mike Noyes <[EMAIL PROTECTED]> > http://sourceforge.net/users/mhnoyes/ > http://leaf.sourceforge.net/content.php?menu=1000&page_id=4 > > > ___ > Leaf-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-devel > ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] Suggestion
Hi, Just want your advise on the following : We have weblet and all the different packages. Weblet gives us info about general system info. For info about the packages we have to look in the different log files, start special shell commands, Shouldn't it be nice if we had a system, which on boottime reads all the different packages, add an entry in the main weblet page (for each packages that as a special weblet entry), thus dynamically creating the main webletpage, pointing to a special webpage for the according package. Just a tought... Stefaan ___ Leaf-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-devel
