Opened 12 years ago

Closed 12 years ago

#89 closed defect (fixed)

Unable to determine whether a package was built

Reported by: k.szczesny@… Owned by: amain
Priority: major Milestone: milestone:
Component: debian/packages Version: 2.0
Severity: Keywords:


When make runs and fails during packages compilation [in my case - libnl], during next run it will assume package was compiled and look for .deb files.
Files don't exist and build fails.
Waiting 30mins just to realize I have to wait another hour - priceless.

Attachments (0)

Change History (5)

comment:1 Changed 12 years ago by stappers

The same request in my words:

When a build fails, shoud the next build attempt continue where the previous build failed.
Debwrt does the next build from square one, the beautifull concept of make is lost.

My workaround:

Look at the toplevel Makefile and see how world is defined:

world: .config openwrt/all debian/rootfs

With that information I did

make debian/rootfs

which builds only the Debian part of Debwrt. ( It jumps beyond square one on a build attempt )

Finer grained build is possible, see ticket #80, comment 1, for an example.

comment:2 Changed 12 years ago by k.szczesny@…

I think you have missed the point.
I am not asking for a 'resume' feature.
I just ask for a proper way of determination whether a package was or was not built.

When you run make and it fails let's say in libnl and you run make again it will NOT try to build libnl again and it will fail when trying to copy deb files which do not exist.

To replicate the issue you will have to get the newest sources, fix the apt-cross bug [add lenny sources and get apt-cross using them] and run make. It will break on libnl.
Then try running make again.

comment:3 Changed 12 years ago by stappers

  • Component changed from debian to buildsystem

comment:4 Changed 12 years ago by amain

  • Component changed from buildsystem to packages
  • Summary changed from Impossible to run make after failed attempt to Unable to determine whether a package was built

I'm aware of some issues with dependencies of make debian/package/all. I'll keep this ticket as a reminder for me to work on it. For now look in the bin/debian directory and see if deb files are there if needed, compare timestamp. On my system it does not take 30 minutes to cross build all DebWrt debian packages. Just a minute or so.

Stappers is correct about the short cut. If you always doe a make V=99, it will also try to build the openwrt part. And (un)fortunately, OpenWrt always creates a firmware image and tries to repackages every enabled package. And that can take a lot of time. On my system about 5 to 10 minutes. For now use variations of:

make debian/rootfs
make debian/package/clean
make debian/package/all
make debian/package/libnl/clean
make debian/package/libnl

Last edited 12 years ago by stappers (previous) (diff)

comment:5 Changed 12 years ago by amain

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in revision #174

Add Comment

Modify Ticket

as closed The owner will remain amain.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.