OpenWrt 18.06.1 build system (the docs are outdated) and not building hostapd-utils, while like hostpad-openssl, which is not even known

[patrikx3]

Hello,

For LEDE, we have a good description for which libraries we have to use to build everything (or like 85%), I am talking about this page:
https://openwrt.org/docs/guide-developer/build-system/install-buildsystem

Now for me, it looks like OpenWrt 18 changed a lot and for example when I build all the packages, it is looks like it missing a lot, that are very important, like for WPS.

In LEDE (build on the links above), I could create WPS.

Now, I use the exact settings, but now it does not build the hostapd-utils_2018-04-09-fa617ee6-5_arm_cortex-a9_vfpv3.ipk package while it is building packages that are not even showing in the http://downloads.openwrt.org/releases/18.06.1/packages/arm_cortex-a9_vfpv3/base repo.

While it built for example - https://cdn.corifeus.com/openwrt/18.06.1/packages/arm_cortex-a9_vfpv3/base/ (missing hostapd-utils_2018-04-09-fa617ee6-5_arm_cortex-a9_vfpv3.ipk):

Like you see, on the release OpenWrt page like hostapd-openssl, hostapd-wolfssl is missing while hostapd-utils_2018-04-09-fa617ee6-5_arm_cortex-a9_vfpv3.ipk is available - http://downloads.openwrt.org/releases/18.06.1/packages/arm_cortex-a9_vfpv3/base:

How can I find out which packages are missing for me in my Docker to build it? Like in the docker I install all possible package with apt, to make sure I can make it work well...

But it looks like from the current docs https://openwrt.org/docs/guide-developer/build-system/install-buildsystem are looks like missing some packages.

Thank you very much.

[patrikx3]

I have installed these packages to build the firmwares:
RUN apt -y install asciidoc bash bc time bcc bin86 binutils build-essential bzip2 cmake curl default-jdk fastjar file flex gawk g++-multilib gcc genisoimage gettext git git-core intltool jikespg libboost-dev libgtk2.0-dev libncurses5-dev libssl-dev libusb-dev libxml-parser-perl make mc mercurial nano ncdu patch perl-modules python python-dev quilt rsync ruby sdcc sharutils software-properties-common sshpass subversion sudo unzip util-linux wget xsltproc xz-utils zlib1g-dev swig

Do you guys what I will be missing?

[patrikx3]

Oh, yes and I am building from Debian Stable (in Docker)

[patrikx3]

So how could I check why it was not building this:
hostapd-utils_2018-04-09-fa617ee6-5_arm_cortex-a9_vfpv3.ipk

It is not in a feed.

[hnyman]

@patrikx3

So how could I check why it was not building this:
hostapd-utils_2018-04-09-fa617ee6-5_arm_cortex-a9_vfpv3.ipk

You could:

• check your .config file. Is that package even included in your build?
• if yes, then what is the error in the build logs. You can enable logging for the build...
• and when running "make V=s", what is the error that gets shown when the failure for that package stops the build.

So far you have not provided any info about your config or the possible error that you are seeing.

First guess is that you have somehow outdated .config and the package is not even tried to be built.

Second guess is that you are actually building from master branch, and you are just wrongly calling it 18.06.1. The whole 18.06 stuff is in a separate branch...

For example, https://cdn.corifeus.com/openwrt/18.06.1/targets/mvebu/cortexa9/packages/ includes base-files_195... that only exists in the master master branch. The 18.06 branch has base files at the 192 version.

18.06 base-files: https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/base-files/Makefile;h=ca1cb47a6cc554c3292aef02f7f86a1c0432f0f7;hb=refs/heads/openwrt-18.06

master:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/base-files/Makefile;h=b72b17ee16763b95558bb8ea78d61a265e863538;hb=HEAD

Similarly, hostapd-openssl now exists in master, when it has been created after the 18.06 was branched off a few months ago.

Randomly changing version designation for the master branch sources produces random results compared to the real 18.06 branch

[patrikx3]

@hnyman

So far you have not provided any info about your config or the possible error that you are seeing.

First guess is that you have somehow outdated .config and the package is not even

thanks so much!
i found the error:

I was doing checkout master after checking the tag version, of course, it was a master build instead of the tagged version and the packages were not building properly. I fixed to the tag.

Thank you so much! I am sure it will work now...