January 2009 - Arch-general - lists.archlinux.org

Re: [arch-general] [arch-dev-public] [signoff] kernel26 2.6.28-3
by Gerhard Brauer 10 Jan '09

10 Jan '09

Am Tue, 06 Jan 2009 17:54:08 +0100 schrieb Thomas Bächler <thomas(a)archlinux.org>: > Aaron Griffin schrieb: > > On Tue, Jan 6, 2009 at 5:08 AM, Tobias Powalowski <t.powa(a)gmx.de> > > wrote: > >> Showstopper: > >> klibc needs to be fixed. It breaks compilation of tools. > > > > Could you be more specific? There was some talk on the klibc ML > > about recent kernel changes, so I'd like to know what is broken. > > Perhaps it is fixable (and Debian may have changes already) > > klibc didn't build against 2.6.28 because some asm headers are now in > arch/x86/include/ instead of include/asm-x86/. I added a quick-fix to > the Makefile so klibc would build. However, I forgot that these > headers weren't installed either, so now klcc does not compile > anything that needs any of those headers (I didn't notice because I > didn't have to recompile the klibc-* packages). This means: klibc > works as a runtime library, but klcc is useless. IMHO is the problem in our kernel26 package. Therein we have a bad symlink to the architecture asm directory. [gerhard@tux1 ~]$ ls -ld /usr/src/linux-2.6.28-ARCH/include/asm lrwxrwxrwx 1 root root 7 26. Dez 11:01 /usr/src/linux-2.6.28-ARCH/include/asm -> asm-x86 [gerhard@tux1 ~]$ ls -l /usr/src/linux-2.6.28-ARCH/include/asm/ -rw-r--r-- 1 root root 5877 26. Dez 10:43 asm-offsets.h If compiling klibc from testing (i use 1.5.15) with the 2.6.28 patch we have in klibc: ----- /usr/lib/klibc/include/asm total 8 lrwxrwxrwx 1 root root 8 2009-01-09 11:54 asm-i386 -> asm-i386 -rw-r--r-- 1 root root 5877 2009-01-09 11:53 asm-offsets.h lrwxrwxrwx 1 root root 7 2009-01-09 11:54 asm-x86 -> asm-x86 ------------ two death symlinks (asm-i386, asm-x86). These are the problems that the other klibc-* tools don't build. But if i change the kernel asm Symlink to: /usr/src/linux-2.6.28-ARCH/include/asm -> /usr/src/linux-2.6.28-ARCH/arch/x86/include/asm (for i686), then i could build a) klibc 1.5.15 without the 2.6.28-patch b) the other klibc-* tools from core. Regards Gerhard

1 1

[arch-general] Problem building Player with pkgbuild
by Christian Babeux 09 Jan '09

09 Jan '09

Hi, I'm trying to build Player with a pkgbuild from the AUR. Here is the pkgbuild: http://aur.archlinux.org/packages/player/player/PKGBUILD Is seems the build is failing because of Arch's strict GCC (I really don't know if that's the problem) At first it was failing with this error: actarrayproxy.cc: In member function ‘player_actarray_actuator_t PlayerCc::ActArrayProxy::GetActuatorData(uint32_t) const’: actarrayproxy.cc:246: error: ‘memset’ was not declared in this scope So I figured that string.h was not included and modified the config.h to include it : echo -e "#include <unistd.h>\n#include <stdlib.h>\n#include <stdio.h>\n#include <string.h>" >> config.h But now it fails with : speechproxy.cc:96: error: ‘strdup’ was not declared in this scope The strange thing is that strdup is declared in string.h... Any ideas ? Christian Babeux

4 3

[arch-general] Kerberos auto renew does not work.
by Anton 08 Jan '09

08 Jan '09

Good Day. I'm trying to make kcm to work but it does not want :-). I want creds on my workstation to be renewed automatically when it near to expire. I set in [libdefaults] secton default_cc_name = KCM:%{uid}, I started kcm. Then I got cred with command: kinit --renewable user1 it gets tgt with a renewable flag but does not renews automatically and then exires. To check this I used -l 60 and/or -r 60. Tgt never be renewed. It always expires. Google did not help me or my search was wrong :-(. What am I doing wrong ? What are the necessary steps should I do to make auto renew of cred ? -- Anton [WARM-RIPE] Stack ltd division head tel. 8 (3822) 555-797

1 0

Re: [arch-general] [arch-dev-public] [signoff] kernel26 2.6.28-2
by pyther 08 Jan '09

08 Jan '09

On Tue, 06 Jan 2009 01:37:33 +0100, tobias(a)justdreams.de wrote: > Quoting Jan de Groot <jan(a)jgc.homeip.net>: >> I'm running the 2.6 prerelease series for a while on my laptop now. My >> first impressions: >> - EXA is even slower than it was with 2.4.3 >> - UXA is much faster >> - XAA not tested >> - 3D is horribly slow >> - Compiz doesn't draw window decorations due to some breakage in libdrm >> >> If we want to use 2.5.x or 2.6 when it comes out, we have to grab a mesa >> snapshot from git master to get GEM support in mesa also. >> >> As xorg-server 1.6 shouldn't be far away anymore, I think we can wait >> for the next stable release of mesa that has GEM support. >> > Just as I thought you have much more insight on this. I totally agree to > stick with 2.4.x for now. > > Thanks, > -T I just wanted to let the devs know that 2.4.x causes Xorg to crash with Kernel 2.6.28, so some users might have issues. It doesn't matter to me either way just wanted to let that information be known. Thanks, pyther

2 2

[arch-general] How to resolve dependency issue - bluez-libs
by richard terry 07 Jan '09

07 Jan '09

This sort of thing always used to be uncommon in Arch. However: Tried to upgrade recently as I do every fe days, got this: looking for inter-conflicts... :: bluez-libs conflicts with bluez. Remove bluez? [Y/n] n error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: bluez-libs: conflicts with bluez If I answer Yes, I get: looking for inter-conflicts... :: bluez-libs conflicts with bluez. Remove bluez? [Y/n] y error: failed to prepare transaction (could not satisfy dependencies) :: gnokii: requires bluez>=4.1 gnokii needed by kdepim etc. How can I resolve this? Any help appreciated. Richard

2 1

Re: [arch-general] [arch-dev-public] WICD, up for grabs
by Grigorios Bouzakis 07 Jan '09

07 Jan '09

On Wed, Jan 07, 2009 at 09:35:14AM +0200, Vesa Kaihlavirta wrote: > > I talked with Angel on IRC and we decided to work on wicd together and > keep it in extra for now. Angel, do you concur? > > And there's a brand new wicd-1.5.8-1 for both arches in testing. > Thanks for keeping it in extra. Is there any reason the new version went to testing first? Greg

2 1

[arch-general] Amarok 2.0 released
by Amanai 07 Jan '09

07 Jan '09

Some of the highlights that are included in the 2.0 release are a completely redesigned user interface, tight integration with online services such as Magnatune, Jamendo, MP3tunes, Last.fm and Shoutcast. There is an overhauled scripting API and plugin support to allow better integration into Amarok. Much of the work has gone into migration from the KDE 3 to KDE 4 framework using core technologies such as Solid, Phonon, and Plasma. http://amarok.kde.org/en/releases/2.0 ftp://ftp.kde.org/pub/kde/stable/amarok/2.0/src/amarok-2.0.tar.bz2

1 1

[arch-general] [signoff] kernel26 2.6.28-3
by Tobias Powalowski 06 Jan '09

06 Jan '09

Hi guys, new kernel adresses the following things: just a quick rebuild which adds crda as optdepend. please signoff for both arches I would like to move in kernel, klibc, mkinitcpio, module-init-tools, crda (with depends) and binary modules this week to core if you are all fine with it. Showstopper: klibc needs to be fixed. It breaks compilation of tools. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

2 1

[arch-general] [signoff] kernel26 2.6.28-2
by Tobias Powalowski 06 Jan '09

06 Jan '09

Hi guys, new kernel adresses the following things: just a quick rebuild which adds crda as optdepend. please signoff for both arches I would like to move in kernel, klibc, mkinitcpio, module-init-tools, crda (with depends) and binary modules this week to core if you are all fine with it. Showstopper: klibc needs to be fixed. It breaks compilation of tools. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

1 0

[arch-general] Building all packages in core
by Baho Utot 05 Jan '09

05 Jan '09

I am presently building all the packages in abs/core against the latest abs kernel, glibc and gcc versions. I think as a goal that the core and extra repositories should be able to build against the latest tools/kernel (in the repos). There has been some failures to build for various reasons. Should I file bug reports or just contact the maintainer for the package? I don't mean to be a pest with this, I am only trying to help. FYI: This is my process: I have constructed a simple bash script that updates abs then rsyncs that to my build subdirectory and then runs makeworld. I have a lockfile so if the process is not complete before it is scheduled to run again, it will not run and skip that day. Upon completion this thing emails me the results both successful builds as well as a list of failures. I will then have a look at the failures and then file bugs reports/contacts if needed. I have placed the script into my crontab which occurs nitely until the bulk of this is complete then I am going to set it to occur every Sunday @ 00:00:00. I will then use this custom repository to keep all my systems here up to date. Thanks.

1 0