gmane.comp.t2.devel

Re: T2 support for BeagleBoard?

René Rebe — 2008-11-30T18:24:04

Hi, t2/trunk:HEAD arm/cortex-a8 optimized binaries just work (tm) on the BeagleBoard (just checked). We only need to factor in the u-book and linux26-omap tree to be able to build everything from scratch for the BeagleBoard. As I know have such a board on my desk I also added a hardware entry to our homepage: http://t2-project.org/hardware/embedded/TI/BeagleBoard/ Enjoy (and patches welcome)! René Rebe wrote:

Re: T2 package for newsbeuter

René Rebe — 2008-11-29T11:23:41

Hi, Koen Vervloesem wrote: Thanks! I only tweaked trailing spaces at some lines, the trailing dot in the Information head-line tag and inserted the build-time percentage into the .cache file from my quick test build (for in-system builds the T2 scripts do not have the binutils reference build time and thus show 100 percent). Committed revision 31396. Have a nice weekend,

Re: New package watchdog

René Rebe — 2008-11-28T08:52:45

Hi, Marian Aldenhövel wrote: Great. I white-space cleaned it a little, added a cache and download checksum: Committed revision 31389. Yours,

Re: New package watchdog

René Rebe — 2008-11-27T18:41:30

Hi, On 27.11.2008, at 18:58, Marian Aldenhövel wrote: I'm just on the way out of the office, so I have not yet taken a closer look, however we have softdog package, but I do not remember to ever use it: http://www.t2-project.org/packages/softdog.html so without further investigation I don't know either if it's the same. You're welcome, too :-) Have a good evening, René

Re: Archivista box - missing mpfr, gmp

René Rebe — 2008-11-27T18:37:08

Hi, On 27.11.2008, at 08:12, helasz< at >gportal.hu wrote: Yeah - thing is, the Archivista Box OS is built with some slightly older, gradually updated T2 scripts that do not yet have gcc-4.3. This is mostly because at the time of creation there was no T2 overloaded package support. You can, of course just modify your local configuration to build it with trunk scripts and packages. Yours,

Archivista box - missing mpfr, gmp

2008-11-27T07:12:09

Hi All, In the target Archivista in trunk due to gcc 4.3.2 mpfr and gmp are required. best regards, helasz

Re: New package My Media System

René Rebe — 2008-11-26T17:40:03

Hi, gx-turbo wrote: Yes, indeed. My log as 12 of them.

Re: New package My Media System

gx-turbo — 2008-11-26T16:59:17

hi René Rene Rebe wrote: yes it built also on my side, although there are errors! I use MMS as audio player since several weeks without problems. I think g++ is used, but it catches the wrong lib. Can you do a grep occasionally on your log please ? I expect something like: error in .../output.o (.eh_frame); no eh_frame_hdr table will be created regards Gerd

Re: New package My Media System

Rene Rebe — 2008-11-26T08:35:23

Hi, sorry for the laggy reply - my desk is rather filled with work :-) gx-turbo wrote: Ah yes, I apparently forgot about it because it had a Priority tag with O(ptional) so it was never built on my integration reference build. I wiped the old copyright lines and added a .cache: Committed revision 31369. I work arounded it with T2 compiler wrappers, reoving them with the next fixed update is of course great. Btw. the -config scripts are old-style and not so prefer (they are not too handy on cross-build, pkg-config for installation data query works better. I added -L/lib* to find -lz, apparently it is not found because the package messes heavily the compiler arguments, and especially some -isystem option appears to let GCC not use the standard system ones. On my side it built. I can imagine such failuers if C++ files are finally linked without g++'s help, but just with ld. Yours,

Re: glibc 2.8

Rene Rebe — 2008-11-25T10:23:55

Well, I prefer real tarball releases, from my point of few glibc maintenance is in big trouble with the wanna be big player just messing with it like they want - without even rleasing tarballs. The situation is like this for years, now - the glibc releases pop up as snapshots in Fedora and the others can see where they get the source from. Of course we can download some CVS tag or snapshot by date - but good project and release maintenance is something else. At least from my point of view. Given they "indicate to have something like a 2.9 release", now, we'll probably update to something like that directly, skipping the 2.8 for which release tarballs never saw the day of light. Btw: I even already contacted RMS some years ago regarding the release pratice of this FSF "flagship" project. On "06/15/2007 10:49 AM" he replied: Btw2: http://freshmeat.net/projects/glibc/ top note Yours, Rene Adam Stirk wrote:

Re: glibc 2.8

Adam Stirk — 2008-11-25T10:14:04

Does that mean that we will be upgrading it to 2.9? :) -----Original Message----- From: René Rebe [mailto:rene< at >exactcode.de] Sent: 24 November 2008 18:46 To: Gerardo Di Iorio Cc: T2 developers mailing list Subject: Re: [t2] glibc 2.8 Hahaha, there now is a tarball-less 2.9: http://freshmeat.net/projects/glibc/?branch_id=3522&release_id=288924 What a fun - have fun, René On 13.11.2008, at 10:14, Gerardo Di Iorio wrote:

Building xen-tools

William Tracy — 2008-11-25T03:32:24

I want to have Qemu on my T2 partition, so I can play with TLX and T2-rescue builds inside the emulator. Qemu depends on xen-tools, which fails to build for me (this is T2 7.0). I've uploaded the log here: http://www.csc.calpoly.edu/~wtracy/9-xen-tools.err The offending vmxassist.tmp has three comments at the front starting with the `#' character. They could be removed without negatively impacing anything else ... but this is a file generated by the build script at compile time, so I can't just edit the file and repeat the build. Argh. These lines could be trivially removed with sed s/\#.*^// but it's not immediately obvious to me how/where I would hook that command into the build. Is this feasible short of hacking inside of the Makefile? compile.patch for this package has a comment from Rene: "Are we the only folks building these tools?" I have to wonder about that, myself.

Re: glibc 2.8

René Rebe — 2008-11-24T18:46:24

Hahaha, there now is a tarball-less 2.9: http://freshmeat.net/projects/glibc/?branch_id=3522&release_id=288924 What a fun - have fun, René On 13.11.2008, at 10:14, Gerardo Di Iorio wrote:

Re: New package My Media System

gx-turbo — 2008-11-24T10:35:51

hi René thanks alot. some remarks: did you see the cxfe package I sent 13.Oct. ? It is an add-on for MMS to play movies with xine. To play sound, xine-lib is enough. There is an additional problem with lirc: see my post 13. Oct. I have not looked into this anymore. Do you have proposal how to proceed with this one ? For MMS itself I have identified 3 problems: 1. imlib not found at config 2. lz/lncurses not found during link 3. .eh_frame missing during link 1. imlib: I made a proposal for a simple patch/change in MMS, It was accepted and should be in at least in final release 1.1.0 (using `imlib2-config --libs`) 2. lz/lncurses: I found a work-around, but was not sure if its generally working (removing some "-Wl,-nostdlib" from makefiles). If you found a good solution, great. It took a while for me to understand that this is independent from #3 .eh_frame. 3. .eh_frame: I still do not understand the details. I still have this error, but mms is working since several weeks without problems. From my und

Re: Can't talk to network--DHCP problem?

René Rebe — 2008-11-24T08:27:52

Hi all, Michael Tross wrote: I like to stress that if this is still lthe case in trunk:HEAD that it's a bug - not a feature. DHCP must work with just the dhcp keyword in Netconf (formerly known as ROCK Net :-) without poking kernel modules or creating another config file such as /etc/dhcpd.conf manually. Guess I should give it a try soonish. Actually I personally find it quite sad how much regressions ^W random changes the DHCP 4.0 package had and how much of our time it already wasted :-( Btw. We have several alternative, saner and tinier DHCP clients in T2, on which I'll probably going to explore more in projects: dhcpclient It's a modern client which also monitors the NIC for link changes and thus intelligently and instantly issues a DHCP request when the cable is plugged in (and not like the classic ISC one 20 minutes later, etc.). Yours,

Re: Can't talk to network--DHCP problem?

William Tracy — 2008-11-24T06:24:50

In case anyone is curious, networking wasn't coming up because my default runlevel was 2. Stone detects eth1 on my machine (my wireless card), but I had to remove that entry from the conf file because the networking init script would try to launch it and hang for ~30 seconds on boot. Also, to my surprise, these days Gmail is acually usable from Links. :-P

Re: Can't talk to network--DHCP problem?

William Tracy — 2008-11-23T23:56:25

I must be going insane. I installed the 7.0-rc2 image, ran ifup eth0, and could wget www.google.com. (eth0 still isn't coming up automatically on boot, but I'm sure I can fix that in a few minutes if I try.) I could *swear* that it wasn't working the last time I installed that image. Go figure. Incidentally, the "Minimal" image includes svn, wget ... and no web browser. I guess my next task is to build Links. :-) Everyone, thanks for your patience.

Re: Can't talk to network--DHCP problem?

William Tracy — 2008-11-23T21:50:17

Okay, I booted the rc1 live image, and was able to get the following output from dhclient: Internet Systems Consortium DHCP Client V3.0.5 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:1a:a0:fd:97:49 Sending on LPF/eth0/00:1a:a0:fd:97:49 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 No DHCPOFFERS received. No working leases in persistent database - sleeping. I'm not sure why it's not able to talk to the DHCP server (I'm online now after rebooting into Fedora, so it's not something simple like a loose cable) but this looks much more solvable than the previous situation.

Re: Can't talk to network--DHCP problem?

Michael Tross — 2008-11-23T11:26:03

Am Samstag, den 22.11.2008, 10:04 -0800 schrieb William Tracy: On trunk there are known problems with the dhcp package since the 4.0.x update, this was discussed earlier this year: http://www.nabble.com/forum/ViewPost.jtp?post=18650084&framed=y You have to setup dhcp client on a target system: - edit and create a valid /etc/dhclient.conf with at least the single line: script "/etc/dhclient-script"; - you may have to preload the IPv6 module in /etc/conf/kernel, depending on your kernel configuration: modprobe ipv6 Somehow the ipv6 module is not automatically loaded, even with alias net-pf-10 ipv6 in /etc/modprobe.conf. Michael

Re: Can't talk to network--DHCP problem?

William Tracy — 2008-11-22T18:04:11

On Sat, Nov 22, 2008 at 2:16 AM, Adam Stirk brantano.co.uk> wrote: I tried that, and that time it complained that it couldn't find '/sbin/dhclient-script'; so I copied /etc/dhclient-script into /sbin, and got the following output: Internet Systems Consortium DHCP Client 4.0.0 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ /sbin/dhclient-script: line 230: [: =: unary operator expected /sbin/dhclient-script: line 240: [: =: unary operator expected /sbin/dhclient-script: line 254: [: =: unary operator expected /sbin/dhclient-script: line 254: [: =: unary operator expected /sbin/dhclient-script: line 266: [: =: unary operator expected /sbin/dhclient-script: line 279: [: too many arguments No broadcast interfaces found - exiting. BTW, I said before that this was a 7.0 install. I confused myself--this is actually a build from Trunk earlier this week. I remember now that the 7.0 rc 2 wasn't wanting to talk to my flash drive

Re: Can't talk to network--DHCP problem?

Adam Stirk — 2008-11-22T10:16:55

I think this is why I load the ipv6 kernel module at startup (Custom rocknet script). You can try 'modprobe ipv6' then 'dhclient eth0'. I can send you a patch for the rocknet script if this is what your problem is. Regards Adam -----Original Message----- From: William Tracy [mailto:afishionado< at >gmail.com] Sent: 22 November 2008 03:43 To: Adam Stirk Cc: T2 developers mailing list Subject: Re: [t2] Can't talk to network--DHCP problem? On Fri, Nov 21, 2008 at 6:50 PM, William Tracy gmail.com> wrote: Okay, I can tweak that file all I want, and it seems to have no effect. I did try dhclient -v, and got this: Internet Systems Consortium DHCP Client 4.0.0 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Error opening '/proc/net/if_inet6' to list IPv6 interfaces; No such file or directory Can't get list of interfaces. If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that