Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - netmap

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: netmap r1324.519c07f-1

Git Clone URL: https://aur-dev.archlinux.org/netmap.git (read-only)
Package Base: netmap
Description: Netmap is a framework for high speed network packet I/O.
Upstream URL: http://info.iet.unipi.it/~luigi/netmap
Licenses: BSD
Submitter: vmaffione
Maintainer: vmaffione
Last Packager: vmaffione
Votes: 4
Popularity: 0.000706
First Submitted: 2013-10-29 15:00
Last Updated: 2016-12-19 18:00

Latest Comments

1 2 3 4 Next › Last »

vmaffione commented on 2016-12-16 10:16

Compilation issue solved for igb.
Now all the netmap-provided drivers are available (e1000, e1000e, igb, ixgbe, i40e, veth, virtio_net, forcedeth).

vmaffione commented on 2016-12-14 12:42

Hi folks,
I updated the netmap package to align with the new netmap build system, which makes the PKGBUILD a lot simpler. All the available patched drivers are currently installed (with a "_netmap" suffix to avoid ambiguity), except for igb, for which there is a compilation issue.

vmaffione commented on 2015-12-26 11:16

Thanks for the nice suggestions! However, taking inspiration from /usr/lib/yaourt/pkgbuild.sh, I think I managed to correctly override makepkg path variables, since I'm now able to build netmap with yaourt. Can you give a try?

I also added a message regarding patched drivers to be shown at install time.
Since I cannot replace the drivers installed by the linux package, one could bypass udev by blacklisting official driver modules and automatically loading patched drivers at boot time.

However, I'm not sure this strategy should be included in the netmap package, since it would possibly conflict with other configuration files in /etc/modprobe.d and /etc/modules-load.d. That's why I think it's best to let the user carry out this configuration manually, to make sure he knows what she is doing. All things considered, this configuration should be done only once.

shallpion commented on 2015-12-26 02:05

Yes I can build it using the standard Arch makepkg way, and I think any future user who ran into this problem would easily figure out any possible workaround based on our discussion :) Or perhaps we can let PKGBUILD to spit out a warning if the users use yaourt.

By the way, do you have any plan to possibly letting arch load patched NIC driver to replace the original one during bootup, so users don't have to do it by themselves? I noticed your PKGBUILD appended _netmap to the .ko modules but apparently they are not loaded by default and it would affect the function of netmap. Perhaps a little warning message about users having to load modules by themselves after the installation would be a lot helpful.

Thanks :)

vmaffione commented on 2015-12-25 22:15

I've done some modification to the PKGBUILD, trying to force SRCDEST variable to the desired value. But I cannot make the thing work with yaourt even in this case.
It keeps using SRCDEST=/tmp/yaourt-tmp-myname/aur-netmap/linux), as you pointed out.

I would say that the easy way is not using yaourt in this case :)
If I understand correctly you are able to build the netmap package with plain makepkg, which is the Arch way, aren't you?

The only thing I can think of is an ugly workaround in build() where I try to detect this situation (sources stored in the different place) before running configure, and change the --kernel-sources argument consequently. But I'm not sure this is better than just require the user to build using makepkg directly - no yaourt.

shallpion commented on 2015-12-25 21:18

Okay I figured it out. If I manually download the snapshot tarball and run makepkg against the PKGBUILD then it will build as normal. It must have been the way AUR package is handled by yaourt which put it in a different location. Is there any way to easily fix this? Thanks..

shallpion commented on 2015-12-25 20:48

I just found the extracted source of Linux, it is located under

/tmp/yaourt-tmp-myname/aur-netmap/linux/src/linux-4.2

instead of

/tmp/yaourt-tmp-myname/aur-netmap/src/abs/core/linux/src/linux-4.2

So manually using this as kernel source in configure worked for me. Still I am puzzled by why my source code was extracted into this location...


shallpion commented on 2015-12-25 20:07

Hi, thanks for the suggestion. I have checked my makepkg.conf but no none of those variables were touched, everything was as the same as default. As I said I also tried to install it on a freshly installed virtual machine but it still didn't work....

vmaffione commented on 2015-12-25 15:23

So you see linux sources being downloaded and patched, but they are not stored in $srcdir/abs/core/linux/ where netmap PKGBUILD assumes they are stored. They must be stored somewherelse.

I suspect your makepkg.conf is configured to download/build/store source files and compiled files in a different directory than the default one (i.e. directory where makepkg is run).

If you take a look at "man makepkg", you will see that there are some environment variables that modify the behaviour of makepkg, like SRCDEST, SRCPKGDEST and BUILDDIR.

Can you check your makepkg.conf and environment variables to make sure those variables are not set?

shallpion commented on 2015-12-25 02:56

I just tried to install netmap on a newly installed fresh archlinux using the latest monthly ISO, still the same issue.. Thanks.