ProAudio repository for Arch users

timbosa · 2007-11-04 04:11:04

funkmuscle wrote:

==> ERROR: Failure while downloading patch-2.6.23.1-rt4.bz2

Try the one in AUR (2.6.23.1-rt5). Ingo's patch can go through several version changes in rapid succession. When you get a downloading error you might have to check the source. If you change

http://www.kernel.org/pub/linux/kernel/ … .x-rtx.bz2 to
http://www.kernel.org/pub/linux/kernel/projects/rt/older/patch-2.6.xx.x-rtx.bz2

it will download.

btartsa wrote:

bad news though...massive performance loss w/ this kernel. my desktop (openbox) is really choppy and even moving an aterm around causes an xrun

Have you tried 2.6.23.1-rt5? People had trouble with rt1-4. Let me know if you still have trouble with it and what hardware you're using. Nice work on the wiki!!

markc wrote:

Solved: I'm not sure how to submit PKGBUILDs to AUR when there is already a PKGBUILD of the same name and purpose

For more information about AUR have a look at
http://wiki.archlinux.org/index.php/New … guidelines
http://aur.archlinux.org/guidelines.html
http://bbs.archlinux.org/viewtopic.php?id=13566
http://bbs.archlinux.org/viewtopic.php?id=8041 gives some insight about the history behind aur and how/why it is what it is today.

Basically if you notice a package is out of date/incorrect you have several options. First of all let the owner of the package know about the problems with it. If that fails and you haven't already tried, update/fix the package to work for you (which you did, well done) and let the owner and other users know about your corrections/recommendations. If you still aren't happy that a package is quite wrong and/or out of date you can request that a TU orphan a package.

So please let me know if my package is out of date or incorrect or you can tell me to get my act together. You have my permission

Last edited by timbosa (2007-11-04 04:11:52)

funkmuscle · 2007-11-04 04:48:43

I did like you said:

patching file drivers/net/pasemi_mac.c
The next patch would create the file include/linux/pickop.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file include/linux/pickop.h.rej
patching file include/asm-x86_64/page.h
The next patch would create the file kernel/rcupreempt-boost.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file kernel/rcupreempt-boost.c.rej
patching file include/linux/list.h
patching file drivers/usb/host/ehci-q.c
patching file kernel/power/poweroff.c
The next patch would create the file include/linux/sched_prio.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file include/linux/sched_prio.h.rej
==> ERROR: Build Failed. Aborting...

don't know what I'm missing???

this is the PKGBUILD:

# Contributor: timbosa <tinny_tim@dodo.com.au>
pkgname=kernel26rt
_basekernel=2.6.23
_kernpatchset=1
_patchver=rt5
pkgver=2.6.23.1_rt5
pkgrel=1
pkgdesc="The Linux Kernel and modules with Ingo Molnar's Realtime Preemption patch"
arch=(i686 x86_64)
license=('GPL2')
url="http://www.kernel.org/pub/linux/kernel/projects/rt/"
backup=('boot/kconfig26rt' etc/mkinitcpio.d/${pkgname}.preset)
depends=('module-init-tools' 'mkinitcpio>=0.5.15')
install=kernel26rt.install
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.23.tar.bz2 \
ftp://ftp.kernel.org/pub/linux/kernel/v … 6.23.1.bz2 \
http://www.kernel.org/pub/linux/kernel/ … .1-rt5.bz2 \
config config.x86_64 \
logo_linux_clut224.ppm \
logo_linux_mono.pbm \
logo_linux_vga16.ppm \
kernel26rt.preset \
mkinitcpio-kernel26rt.conf)
md5sums=('2cc2fd4d521dc5d7cfce0d8a9d1b3472'
'896c5d4e7fd68d37b8c16e5d2842563b'
'2dd9532c1ea1ecd83e53a2cb7b4ffec1'
'c9fe169db354b8bc1bb7b9ff06dc876f'
'797443c1f954feefb413be2f8ab4181b'
'5a62bcc7e96601052c7405459b483826'
'ed6b42fea2f5d27f7eb920746ccc1ebb'
'a995ec849ea43d3c89d607bbdd1e7d09'
'cdd412aaac5bf7b057d160f11536770a'
'36858bd6a0bca63d2aa901b2e42d4a05')

build() {
[ "${CARCH}" = "i686" ] && KARCH=i386
[ "${CARCH}" = "x86_64" ] && KARCH=x86_64

cd $startdir/src/linux-$_basekernel
# add upstream patch from 2.6.23 series
patch -Np1 -i ../patch-$_basekernel.$_kernpatchset || return 1
# add realtime patch
patch -Np1 -i ../patch-$_basekernel.$_kernpatchset-$_patchver || return 1
# add other patches here
#patch -Np1 -i ../patch-xyz

# remove the extraversion from Makefile
sed -i 's|^EXTRAVERSION = .*$|EXTRAVERSION ;s|-rt||g' Makefile
# Arch logo!
cp ../logo_linux_clut224.ppm drivers/video/logo/
cp ../logo_linux_mono.pbm drivers/video/logo/
cp ../logo_linux_vga16.ppm drivers/video/logo/
if [ "$CARCH" = "x86_64" ]; then
cat ../config.x86_64 >./.config
else
cat ../config >./.config
fi
# build the full kernel version to use in pathnames
. ./.config
_kernver="${_basekernel}${CONFIG_LOCALVERSION}"
# load configuration
yes "" | make config
make menuconfig
#make gconfig
#make xconfig
# build!
make bzImage modules || return 1
mkdir -p $startdir/pkg/{lib/modules,boot}
make INSTALL_MOD_PATH=$startdir/pkg modules_install || return 1
cp System.map $startdir/pkg/boot/System.map26rt
cp arch/$KARCH/boot/bzImage $startdir/pkg/boot/vmlinuz26rt
install -D -m644 Makefile \
$startdir/pkg/usr/src/linux-${_kernver}/Makefile
install -D -m644 kernel/Makefile \
$startdir/pkg/usr/src/linux-${_kernver}/kernel/Makefile
install -D -m644 .config \
$startdir/pkg/usr/src/linux-${_kernver}/.config
install -D -m644 .config $startdir/pkg/boot/kconfig26rt
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/include

for i in acpi asm-{generic,i386,x86_64} config linux math-emu media net pcmcia scsi sound video; do
cp -a include/$i $startdir/pkg/usr/src/linux-${_kernver}/include/
done

# copy files necessary for later builds, like nvidia and vmware
cp Module.symvers $startdir/pkg/usr/src/linux-${_kernver}
cp -a scripts $startdir/pkg/usr/src/linux-${_kernver}
# fix permissions on scripts dir
chmod og-w -R $startdir/pkg/usr/src/linux-${_kernver}/scripts
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/.tmp_versions

mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel
cp arch/$KARCH/Makefile $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
if [ "$CARCH" = "i686" ]; then
cp arch/$KARCH/Makefile.cpu $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/
fi
cp arch/$KARCH/kernel/asm-offsets.s $startdir/pkg/usr/src/linux-${_kernver}/arch/$KARCH/kernel/

# add headers for lirc package
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video
cp drivers/media/video/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/
for i in bt8xx cpia2 cx25840 cx88 em28xx et61x251 pwc saa7134 sn9c102 usbvideo zc0301; do
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/$i
cp -a drivers/media/video/$i/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/media/video/$i
done
# add dm headers
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/drivers/md
cp drivers/md/*.h $startdir/pkg/usr/src/linux-${_kernver}/drivers/md
# add inotify.h
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/include/linux
cp include/linux/inotify.h $startdir/pkg/usr/src/linux-${_kernver}/include/linux/
# add CLUSTERIP file for iptables
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/net/ipv4/netfilter/
cp net/ipv4/netfilter/ipt_CLUSTERIP.c $startdir/pkg/usr/src/linux-${_kernver}/net/ipv4/netfilter/
# add wireless headers
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/net/mac80211/
cp net/mac80211/*.h $startdir/pkg/usr/src/linux-${_kernver}/net/mac80211/
# add vmlinux
cp vmlinux $startdir/pkg/usr/src/linux-${_kernver}
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p $startdir/pkg/usr/src/linux-${_kernver}/`echo $i | sed 's|/Kconfig.*||'`
cp $i $startdir/pkg/usr/src/linux-${_kernver}/$i
done

cd $startdir/pkg/usr/src/linux-${_kernver}/include && ln -s asm-$KARCH asm

chown -R root.root $startdir/pkg/usr/src/linux-${_kernver}
find $startdir/pkg/usr/src/linux-${_kernver} -type d -exec chmod 755 {} \;
cd $startdir/pkg/lib/modules/${_kernver} && \
(rm -f source build; ln -sf ../../../usr/src/linux-${_kernver} build)
# install fallback mkinitcpio.conf file and preset file for kernel
install -m644 -D $startdir/src/kernel26rt.preset $startdir/pkg/etc/mkinitcpio.d/kernel26rt.preset || return 1
install -m644 -D $startdir/src/mkinitcpio-kernel26rt.conf $startdir/pkg/etc/mkinitcpio.d/kernel26rt-fallback.conf || return 1
# set correct depmod command for install
sed -i -e "s/KERNEL_VERSION=.*/KERNEL_VERSION=${_kernver}/g" $startdir/kernel26rt.install
echo -e "# DO NOT EDIT THIS FILE\nALL_kver='${_kernver}'" > ${startdir}/pkg/etc/mkinitcpio.d/kernel26rt.kver

# remove unneeded architectures
rm -rf $startdir/pkg/usr/src/linux-${_kernver}/arch/{alpha,arm,arm26,avr32,blackfin,cris,frv,h8300,ia64,m32r,m68k,m68knommu,mips,parisc,powerpc,ppc,s390,sh,sh64,sparc,sparc64,um,v850,xtensa}
}

Last edited by funkmuscle (2007-11-04 04:50:08)

timbosa · 2007-11-04 05:58:13

funkmuscle wrote:

The next patch would create the file include/linux/sched_prio.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file include/linux/sched_prio.h.rej
==> ERROR: Build Failed. Aborting...

This would indicate that a patch has already been applied... Try removing src/ & pkg/ and re-run makepkg.

rm -R src/ pkg/ && makepkg

funkmuscle · 2007-11-04 15:17:03

I removed th entire directory now this:
Please, set EDITOR variable
==> ERROR: install scriptlet (kernel26rt.install) does not exist.

timbosa · 2007-11-05 02:11:41

funkmuscle wrote:

I removed th entire directory...
==> ERROR: install scriptlet (kernel26rt.install) does not exist.

What files do you have? It appears that kernel26rt.install is missing. If you extracted the package from AUR you should have ended up with a directory called 'kernel26rt' and the following files within:

PKGBUILD
config
config.x86_64
kernel26rt.install
kernel26rt.preset
logo_linux_clut224.ppm
logo_linux_mono.pbm
logo_linux_vga.ppm
mkinitcpio-kernel26rt.conf

You need these files for makepkg to work. If you are missing any of these files maybe just remove the directory entirely and start again. Try the following

wget -c http://aur.archlinux.org/packages/kernel26rt/kernel26rt.tar.gz
tar -xzf kernel26rt.tar.gz
cd kernel26rt
makepkg

funkmuscle · 2007-11-05 12:17:04

missing the kernel26rt.install. I know I need that for it to work.
Where can I get that from? That was part of the earlier kernel26rt on the AUR.
All the other others are there and I had them already.

markc · 2007-11-05 15:22:31

timbosa wrote:

Basically if you notice a package is out of date/incorrect you have several options. First of all let the owner of the package know about the problems with it. If that fails and you haven't already tried, update/fix the package to work for you (which you did, well done) and let the owner and other users know about your corrections/recommendations. If you still aren't happy that a package is quite wrong and/or out of date you can request that a TU orphan a package.

A great summary of those AUR howto links, thanks So perhaps I should have logged onto AUR and posted my PKGBUILD mods to a comment on the kernel26rt page? Could be messy, it's easier to paste code into this forum using BBS code. Ah ha, there is a flag-as-outofdate option which I presume you get some kind of notice of.

Is there any chance the source packages could be kept under Git, SVN or perhaps rsyncable (or all 3) from somewhere ?

If nothing else I would suggest http://code.google.com/hosting/createProject which comes with subversion, forum and wiki etc.

markc · 2007-11-05 15:33:39

FWIW this is a subtle point that might be worth considering. Note the slightly different usage of _kernpatchset in the 2nd version. The reason I use the 2nd version is so that it also covers first release kernels before the first kernel patchset comes out.

_basekernel=2.6.23
_kernpatchset=1
_patchver=rt5
http://www.kernel.org/pub/linux/kernel/projects/rt/patch-$_basekernel.$_kernpatchset-$_patchver.bz2 \

_basekernel=2.6.23
_kernpatchset=.1
_patchver=rt5
http://www.kernel.org/pub/linux/kernel/projects/rt/patch-$_basekernel$_kernpatchset-$_patchver.bz2 \

timbosa · 2007-11-06 07:20:23

funkmuscle wrote:

missing the kernel26rt.install. I know I need that for it to work.
Where can I get that from? That was part of the earlier kernel26rt on the AUR.

It still is. Are you getting the files from the sources section? If you are I wouldn't recommend it, always download the tarball and extract. It's the best way to be sure you get all the files needed. Many packages don't list various files included inside the package as a source (I can see how this can cause confusion) and don't show up under sources on the packages AUR page.

In future I'll list all files as a source to avoid problems like this but I still think using packagename.tar.gz is the only way you should get the package.

markc wrote:

So perhaps I should have logged onto AUR and posted my PKGBUILD mods to a comment on the kernel26rt page? Could be messy, it's easier to paste code into this forum using BBS code.

You could also use pastebin if you wanted http://pastebin.archlinux.org/

I don't think svn or the like would quite be practical for something as simple as kernel26rt but is an interesting thought.

FWIW this is a subtle point that might be worth considering. Note the slightly different usage of _kernpatchset in the 2nd version.

This makes complete sense and I will include it in future versions. Thanks

funkmuscle · 2007-11-06 12:27:59

timbosa, thanx man but you solved it for me earlier.
I did your:

wget -c http://aur.archlinux.org/packages/kerne … 6rt.tar.gz
tar -xzf kernel26rt.tar.gz
cd kernel26rt
makepkg

kernel running fine. Just takes forever to load X. all the RT kernels did except the first one made.

Yeah guys, keep up the great, amazing, awesome work..................
Thanx a million for people like yourselves...:D

Last edited by funkmuscle (2007-11-07 14:32:48)

markc · 2007-11-06 13:24:41

Folks, I dived in and created a project at http://code.google.com/p/proaudio/. I didn't mean to call the project "proaudio" as I first tried "rtaudio" but that name was taken and when I simply tried "proaudio" (for the hell of it) it just went ahead and created the project. I am personally only concerned with the core audio system and not so much with applications, and also interested to use the Google Code site to see how well, or not, it works. The project statement is (so far)...

This set of Archlinux PKGBUILD based source packages will provide and up to date linux kernel with patches to include the latest usable (read: almost stable, or, good enough to use) ALSA and JACKd subsystem. The emphasis is on providing the latest releases in a timely fashion via a rolling release schedule based on Subversion checkouts and user/developer interaction using the Google Code facilities.

The idea is that anyone, with a Google account, can join the project and update the Subversion repo and easily discuss any changes. A log of any repo updates goes into a proaudio-devel Google discussion group which provides a RSS feed, so, most importantly, svn update modifications have an easy to monitor RSS feed. There is also a proaudio-users group for svn log-free discussion, along with a wiki and a simple issue tracker. It's mainly for the ability to group manage the core proaudio packages and allow multiple users to update those source packages and for anyone else to be able to IMMEDIATELY and incrementally (ie; very easily) update their own working copy of the centralised repo packages... and, to be able to monitor svn and discussion activity via RSS feeds.

All I have done so far is import these packages to http://proaudio.googlecode.com/svn/trunk/ and checked them out again so now I can start doing some testing and I'll push through any changes I make from my local copy. Anyone is welcome to checkout the packages, which is best done by cd /var/abs/local followed by svn checkout http://proaudio.googlecode.com/svn/trunk/ proaudio then cd proaudio and makeall. From then on an update is simply done by cd'ing back into the proaudio directory and issuing svn up. If anyone wants to actively update the repo then just ask me here or in proaudio-devel group (email or web interface) and I'll formally add you to the project.

markc · 2007-11-06 15:19:35

In case anyone is wondering "why bother with yet another repo" then here's an example of an update to the alsa-tools package... anyone can see EXACTLY what I did for this particular update and I get an email notification as well as an RSS feed for this group, so I can't miss a package update. All I did was build the checked out package as I normally would, by modifying the PKGBUILD && makepkg, then did a svn up where an editor popped up for me to add a comment and the rest is automatic.

http://groups.google.com/group/proaudio … ea63?hl=en

and the PKGBUILD file itself can be viewed from here...

http://proaudio.googlecode.com/svn/trun … s/PKGBUILD

and here is the output of svn up ; svn log in a local checked out copy, again, so easy to keep track of what's going on.

root@minuet.lan /var/abs/local/proaudio svn log
------------------------------------------------------------------------
r4 | mconstable | 2007-11-07 00:44:49 +1000 (Wed, 07 Nov 2007) | 2 lines

Updated to version 1.0.15 and skipped qlo10k1 until it's updated

------------------------------------------------------------------------
r3 | mconstable | 2007-11-07 00:14:02 +1000 (Wed, 07 Nov 2007) | 2 lines

Updated to version 1.0.15 and normalized a few fields.

------------------------------------------------------------------------
r2 | mconstable | 2007-11-06 20:42:12 +1000 (Tue, 06 Nov 2007) | 2 lines

Initial import of various source packages from AUR and core/extra.

------------------------------------------------------------------------
r1 | (no author) | 2007-11-06 15:52:58 +1000 (Tue, 06 Nov 2007) | 1 line

Initial directory structure.
------------------------------------------------------------------------

markc · 2007-11-07 06:26:02

Well so far I have built (and now rebooted) on these source packages and updated the Subversion repository accordingly. I am confused with the JACK package I am running as I have a 0.107.2 but the package in extra seems to be 0.103 so I need to work out where I got my 0.107.2 version from. If anyone knows which later SVN revision is good enough to use then perhaps a jackd-svn source package might be more useful than an updated jack-audio-connection-kit package.

alsa-firmware/
alsa-lib/
alsa-oss/
alsa-plugins/
alsa-tools/
alsa-utils/
fxload/
irqbalance/
kernel26rt/
makeall
nvidia-rt/

To view the actual files...

http://proaudio.googlecode.com/svn/trunk/

To see the commit log and diffs...

http://groups.google.com/group/proaudio … ics?start=

and to download the packages...

pacman -S subversion
cd /var/abs/local
svn checkout http://proaudio.googlecode.com/svn/trunk/ proaudio
cd proaudio
makeall # not tested yet

I will also make this suite available as binary packages as soon as I work out the right JACK package. I'll probably include freebob and some other JACK related utilities next... meterbridge, qjackctl and jackrack for example... perhaps jackmp (alternative C++ jack deamon) and netjack as well.

Update: Just added a jackd-svn package to replace the standard jack-audio-connection-kit and it is currently at version 0.107.5 or revision 1062.

Last edited by markc (2007-11-07 09:52:58)

timbosa · 2007-11-07 09:26:36

kernel26rt has been updated to 2.6.23.1-rt7. A few things... Currently there are 3 versions of the realtime patch. Developers have differing views about the best method for handling RT task balancing between CPU's which people have had problems with. So the differnces between the patches are as follows.

2.6.23.1-rt7 various fixes
2.6.23.1-rt8 features more aggressive RT balancing
2.6.23.1-rt9 feautres RT balancing by CPU priorities
I've put diffenent copies of kernel26rt at http://arch.timbosa.com/download/

If anyone is interested in comparing the 3 with cyclictest (http://git.kernel.org/?p=linux/kernel/g … ;a=summary) the developers I'm sure would love results as to which gives better results. Let me know if you'd like to run some tests.

markc wrote:

Folks, I dived in and created a project at http://code.google.com/p/proaudio/

Interesting stuff mark. I'm curious to see how well google code can work too, so I sent you an email.

Last edited by timbosa (2007-11-07 10:03:29)

btartsa · 2007-11-07 16:27:14

timbosa: I'd like to do some testing on these different patchsets

Will these install in parallel? If not, can you tip me on how not to overwrite existing kernels? This has always been a bit of an issue for be building kernels w/ abs.

Thanks for all you effort guys! Hop on #archlinux-proaudio on freenode!

markc · 2007-11-08 02:29:08

btartsa wrote:

Will these install in parallel?

Good question. I just tried by simply changing pkgname=kernel26-rt7 and that built a kernel package with a separate name but most of the content conflicted with the currently installed kernel package. A little deeper PKGBUILD hacking is required and it seems the path name that various parts get installed into is built up as linux-$_kernver where $_kernver is defined as _kernver="${_basekernel}${CONFIG_LOCALVERSION}" so I presume CONFIG_LOCALVERSION is returning just "rt".

Has anyone got a clue how to force CONFIG_LOCALVERSION to some arbitrary value like rt7, rt8 or rt9 ?

Also, bonus question, has anyone dug deeper into the currently supplied kernel config ? I think it's been carried over from a non-rt kernel with perhaps a few tweaks like increasing hi-res timers to 1024htz etc. I know the original rt PKGBUILD calls up menuconfig to allow the end user to modify the config settings but that presumes the end-user has some clue about what to change and that is such a daunting array of options I don't think it's fair to expect most end users to even have to consider the possibilities. I changed the svn copies to use oldconfig so a build can go all the way through without manual intervention and with the idea that someone who needs to make config changes will be astute enough to know how and where to edit the PKGBUILD to change oldconfig back to menuconfig.

Update: doh, it's a variable in the config file itself so changing it to something like "-rt7" etc will do the trick.

Last edited by markc (2007-11-08 03:05:37)

timbosa · 2007-11-08 06:20:46

btartsa wrote:

timbosa: I'd like to do some testing on these different patchsets...
Will these install in parallel?

Great. I thought about installing them in parallel to each other this morning so I created three different packages named kernel26rttest1, kernel26rttest2, kernel26rttest3. They are at
http://arch.timbosa.com/download/kernel26rttest/

**I'll provide more info about actually running the tests later.**
See below

markc wrote:

Also, bonus question, has anyone dug deeper into the currently supplied kernel config ?

Basically the config was originally copied from the default arch kernel as a base so that boot would run as smoothly as possible for as many as possible. Then tweaks were made based on looking at other distro's realtime kernels, CCRMA I think, I think I looked at maybe JAD (opensuse) as well.

The config is not ideal I know, I thought menuconfig would give users the option to adjust the kernel to their liking, the RT Wiki gives recommendations. With the svn version you shouldn't have to add 'make oldconfig'. Just commenting out make menuconfig will allow the build to continue to completion.

EDIT
Okay. Here's information for running cyclictest:
http://arch.timbosa.com/download/kernel … test-howto

Last edited by timbosa (2007-11-08 07:48:56)

markc · 2007-11-08 07:54:33

timbosa wrote:

I thought about installing them in parallel to each other this morning so I created three different packages named kernel26rttest1, kernel26rttest2, kernel26rttest3.

I've added them, unchanged, to the svn repo along with a new package called rt-tests that you linked to above. It includes the 2 binaries called cyclictest and signaltest with no documentation on how to use them.

**I'll provide more info about actually running the tests later.**
Okay here's information for running cyclictest: http://arch.timbosa.com/download/kernel … test-howto

I missed the above point when I created the rt-tests Git PKGBUILD. I'll add the above sometime later, or maybe someone else can now :-)

The config is not ideal I know, I thought menuconfig would give users the option to adjust the kernel to their liking, the RT Wiki gives recommendations. With the svn version you shouldn't have to add 'make oldconfig'. Just commenting out make menuconfig will allow the build to continue to completion.

Okay, so no *config option defaults to oldconfig behaviour. What about using the current non-rt kernels default config(s) and providing patches to modify them for real-time kernel needs, then anyone can see from the patch what are specific rt changes to the config file and that patch might still aply to the next generation kernels (2.6.24 etc) ?

funkmuscle · 2007-11-08 18:37:17

anyone heard or use this:
zynjacku
http://home.gna.org/zynjacku/

cool, thanx berkus:)

Last edited by funkmuscle (2007-11-10 15:55:39)

berkus · 2007-11-10 14:40:17

funkmuscle, yes, this is modularized lv2 rewrite of zynaddsubfx.

berkus · 2007-11-10 14:41:21

I've uploaded my pkgbuilds to http://arch.madfire.net/proaudio/pkgbuilds/ per markc request and he is building x86_64 packages now.

markc · 2007-11-11 05:18:54

Regarding amsynth, I first had an error that the PKGBUILD needs an arch line so I added both i686 and x86_64, I also needed gtk and gtkmm as dependencies (perhaps they should be makedepends) and then I got this error which looks like hacking on the code or headers to resolve. The source tarball for this 1.2.0 package is nearly 2 years old using gtk1. I think the question I want to ask is, is this package worth supporting and, if so, does it compile cleanly for anyone else ?

PresetControllerView.cc:24: warning: deprecated conversion from string constant to 'char*'
PresetControllerView.cc:28: warning: deprecated conversion from string constant to 'char*'
make[3]: *** [PresetControllerView.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/home/abs/local/proaudio/a/amsynth/src/amSynth-1.2.0/src/GUI'
make[2]: *** [all-recursive] Error 1

Also, as for the x86_64 binary packages, I am using a fairly aggressive CFLAGS setting for the compiler so I suspect (assuming they run okay and so far they do on my machine) I need to compile quite a lot of other support packages so that whole toolset chains are compiled with the same compiler flags... and to be pedantic, that would mean re-compiling all of AL and (in my case) KDEmod as well.

# grep CFLAGS /etc/makepkg.conf
CFLAGS="-march=athlon64 -O2 -msse3 -mfpmath=sse,387 -pipe -ffast-math -m64"
CXXFLAGS=$CFLAGS

Here's another one that has failed to build, chionic. Again, I had to add an arch line. Is chionic compiling for anyone else ?

Package sigc++-1.2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `sigc++-1.2.pc'
to the PKG_CONFIG_PATH environment variable
No package 'sigc++-1.2' found

And yet another one I'm not sure what to do with. I've never even heard of "clam" before and I'm having to install a lot of dependencies I would rather not have on my main workstation if I don't really need them. I really think there should be some kind of proaudio meta PKGBUILD that installs *all* dependencies for the proaudio set of source packages and some of the current 46 packages (perhaps) dropped or reconsidered. Personally, I really only want ardour, rosegarden skype and audacity (or some better gui wav editor) plus ffmpeg, kdenlive and blender... this is my main toolset and most of them are not even included with this current set of packages.

# /var/abs/local/proaudio/c/clam-svn makepkg
==> Making package: clam-svn 20070708-1 (Sun Nov 11 15:43:22 EST 2007)
==> Checking Runtime Dependencies...

==> Missing Dependencies:
   -> fftw2
   -> xerces-c
   -> id3lib
   -> portaudio
==> Checking Buildtime Dependencies...
==> ERROR: could not resolve all dependencies.

# /var/abs/local/proaudio/c/clam-svn pacman -S fftw2 xerces-c id3lib portaudio
error: 'portaudio': not found in sync db

Questions:
* what should I do with packages that do not cleanly compile first go ?
* how far back (deep) should any dependencies be also included ?
* what to do about other packages not already included (ie; ardour, rosegarden) ?
* any comments about how audio dependent video packages could be included (ie; kdenlive, blender) ?

Last edited by markc (2007-11-11 06:42:48)

funkmuscle · 2007-11-11 05:44:23

I may have missed sonething but can someone clarify something for me,
is the new proaudio that markc working on only for x86_64?

I think it's awesome work that all you guys are doing. The most I can do is be a tester. Hope that's cool!!

markc · 2007-11-11 06:31:14

funkmuscle wrote:

I may have missed sonething but can someone clarify something for me, is the new proaudio that markc working on only for x86_64?

berkus created the original set of binary packages which are hosted at http://arch.madfire.net/proaudio/i686/ and started in March of 2007. I started to upload some packages, mainly the rt kernel + alsa + jack, to a Subversion repository at Google Code just this past week. I now have berkus's original set of 46 source packages and am going thru them to compile a set of 64bit binaries which I will push to berkus's site above (in a x86_64 directory) and I will also push all or most of these source packages to the Subversion repo. Hopefully you and others will start using the Subversion repo which will make it a lot easier to both read from and write to the source packages... ie; getting them using svn checkout is easy, and updating the main repo with svn commit is also too easy, and allows for any number of interested folks to maintain the proaudio packages rather than a single person... so the packages should be more uptodate and easier for an end-user to simply "svn up" to update to those latest changes (as opposed to chasing up some source packages from AUR to make an essential change or upstream update).

To answer your specific question, the source packages from the Subversion repo will build either i686 or x86_64 binary packages depending on your platform (or what your /etc/makepkg.conf says your arch is) and both binary sets of packages (inc x86_64 eventually) will be availble from berkus's madfire.net site and hopefully other mirrors as well. I'll also set up a binary host but I'm not sure exactly what set of packages I want to host there at the moment.

funkmuscle wrote:

is the new proaudio that markc working on only for x86_64

And to be clear about the above, I did not mean to set up a Subversion repo using the label "proaudio", I tried to use "rtaudio" but that was already taken and I accidentily used "proaudio" and that was accepted. Point being my original intent was to only create a core kernel + alsa + jack set of packages but it seems now that incorporating berkus's packages as well would be a good idea. I am absolutely convinced (after a week) that using the Google Code Subversion repository method is sooo much better than dealing with AUR, let alone source packages that are not even publically available.

Anyone, just ask if it's not clear how to interact with (read from and/or write to) the Google Code Subversion repository. The only mild downside is that anyone wanting write privileges needs to have a Google ID (like @gmail.com) but anyone else is free to simply checkout (or export) the repo to build their own packages. If anyone wants write/update privs, and has a Gmail account, then pop into #archlinux-proaudio and paste your gmail ID (or in this forum thread) and you'll be able to update the Subversion repo. Any changes made to the source packages are VERY visible to anyone else involved, so catching typos and bugs is easy, so "anyone can update the repo" is open to literally anyone at this stage.

Last edited by markc (2007-11-11 06:40:24)

funkmuscle · 2007-11-11 14:35:30

love the work markc, the first time you posted the info, I started to use the google repo.
Like I said, I can't do what you guys do but I can test the packages and so far, love it all.
everything works great fo me.

one question, what are the differences between to jack packages?
Hopefully we'll get an Arch Multimedia release.
I've tried the other distros the are multimedia based and none works as well as Arch and the work from you guys.
The Packman repo for SuSE has tons of audio apps.

Arch Linux

#276 2007-11-04 04:11:04

Re: ProAudio repository for Arch users

#277 2007-11-04 04:48:43

Re: ProAudio repository for Arch users

#278 2007-11-04 05:58:13

Re: ProAudio repository for Arch users

#279 2007-11-04 15:17:03

Re: ProAudio repository for Arch users

#280 2007-11-05 02:11:41

Re: ProAudio repository for Arch users

#281 2007-11-05 12:17:04

Re: ProAudio repository for Arch users

#282 2007-11-05 15:22:31

Re: ProAudio repository for Arch users

#283 2007-11-05 15:33:39

Re: ProAudio repository for Arch users

#284 2007-11-06 07:20:23

Re: ProAudio repository for Arch users

#285 2007-11-06 12:27:59

Re: ProAudio repository for Arch users

#286 2007-11-06 13:24:41

Re: ProAudio repository for Arch users

#287 2007-11-06 15:19:35

Re: ProAudio repository for Arch users

#288 2007-11-07 06:26:02

Re: ProAudio repository for Arch users

#289 2007-11-07 09:26:36

Re: ProAudio repository for Arch users

#290 2007-11-07 16:27:14

Re: ProAudio repository for Arch users

#291 2007-11-08 02:29:08

Re: ProAudio repository for Arch users

#292 2007-11-08 06:20:46

Re: ProAudio repository for Arch users

#293 2007-11-08 07:54:33

Re: ProAudio repository for Arch users

#294 2007-11-08 18:37:17

Re: ProAudio repository for Arch users

#295 2007-11-10 14:40:17

Re: ProAudio repository for Arch users

#296 2007-11-10 14:41:21

Re: ProAudio repository for Arch users

#297 2007-11-11 05:18:54

Re: ProAudio repository for Arch users

#298 2007-11-11 05:44:23

Re: ProAudio repository for Arch users

#299 2007-11-11 06:31:14

Re: ProAudio repository for Arch users

#300 2007-11-11 14:35:30

Re: ProAudio repository for Arch users

Board footer