I'm trying to compile my own package, i ran make menuconfig to check its selected, then make. it dowloads *.tar.gz off my http server but comes up with this error:

        CFLAGS="-Os -pipe -mips32 -mtune=mips32 " \
        CPPFLAGS="-I/home/fireice/myapps/openwrt/staging_dir_mipsel/usr/include" \
        LDFLAGS="-L/home/fireice/myapps/openwrt/staging_dir_mipsel/usr/lib" \
        ./configure \
          --target=mipsel-linux \
          --host=mipsel-linux \
          --build=x86_64-pc-linux-gnu \
          --program-prefix="" \
          --program-suffix="" \
          --prefix=/usr \
          --exec-prefix=/usr \
          --bindir=/usr/bin \
          --datadir=/usr/share \
          --includedir=/usr/include \
          --infodir=/usr/share/info \
          --libdir=/usr/lib \
          --libexecdir=/usr/lib \
          --localstatedir=/var \
          --mandir=/usr/share/man \
          --sbindir=/usr/sbin \
          --sysconfdir=/etc \
           \
          --disable-nls \
);
/bin/sh: ./configure: No such file or directory

Can someone please tell me if im doing anything wrong?

Seems it can't find the configure script.

Btw. the easiest way to build your own packages is by using the OpenWrt SDK.

Thats what I followed.. but am i suppose to create my own .configure script for make to work?

Look at ./package/strace/Makefile in the SDK. Hint:

$(PKG_BUILD_DIR)/.configured:
    (cd $(PKG_BUILD_DIR); rm -rf config.cache; \
        $(TARGET_CONFIGURE_OPTS) \
        CFLAGS="$(TARGET_CFLAGS)" \
        CPPFLAGS="-I$(STAGING_DIR)/usr/include" \
        LDFLAGS="-L$(STAGING_DIR)/usr/lib" \
        ./configure \
        ... \
    )
    touch $@

Don't forget to generate a ./configure script using the proper tools. This script is the result from parsing a shitload of M4 input files through the socalled autoconf/automake tools. I keep forgetting what goes where and in what order, but in the package you're trying to build there should be a README or an INSTALL file which tells you what to do. I suggest reading up on autotools and/or reading the package documentation.

(Last edited by PolarWolf on 15 Nov 2005, 12:57)