makepkg can not build correctly while *configure && make* works fine.

fuz · 2013-12-17 06:42:39

I planned to build a AUR package for the Click Modular Router from UCLA(http://www.read.cs.ucla.edu/click/). And I wrote the PKGBUILD like bellow:

pkgname="click"
pkgver="2.0.1"
pkgrel=1
pkgdes="Click Modular Router from UCLA."
arch=("i686"
	  "x86_64"
	  "mips64el")
source=("http://www.read.cs.ucla.edu/click/click-2.0.1.tar.gz")
md5sums=("bc43b24b3565b760eebe20f109817f19")

build() {
	cd $srcdir/$pkgname-$pkgver/
	./configure --enable-all-elements
	make
}

package() {
	make DESTDIR=$pkgdir install
}

and then I execute makepkg, a error accured like:

In file included from ../include/click/ipaddress.hh:7:0,
                 from ../include/click/packet.hh:4,
                 from ../include/click/element.hh:7,
                 from ../include/click/router.hh:4,
                 from ../lib/nameinfo.cc:24:
../include/clicknet/ip.h:31:5: error: #error "unknown byte order"
 #   error "unknown byte order"
I saw all the output of makepkg, And I found sevaral lines like :
checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking endianness... 0

It seems that ./configure cannot detect the endianness of the host properly, because 0 is UNKNOWN endianness in the definition.

but what's the ridiculus is when I change the source directory and execurte ./configure && make manually, It works just fine! And bellow is the endianness output lines of ./configure

checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking endianness... 1234
1234 refers to big-endian in the definition.

Does anyone know What the problem with this? Or is it just a BUG of makepkg?

edit: added code tags /Xyne

Last edited by Xyne (2013-12-17 18:22:13)

jasonwryan · 2013-12-17 06:57:40

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Fo … s_and_Code

Scimmia · 2013-12-17 07:00:33

Try it with options=('!buildflags')

fuz · 2013-12-17 12:14:25

I add the options tag in my PKGBUILD, and it works. Many thanks to you.

Scimmia wrote:

Try it with options=('!buildflags')

fsckd · 2013-12-17 15:00:58

As you have found a solution, please mark this thread [solved], Forum Etiquette: How ti Post.

Arch Linux

#1 2013-12-17 06:42:39