Common mistakes in a recipe: Difference between revisions
Jump to navigation
Jump to search
m (What not to do in a recipe moved to Common mistakes in a recipe) |
m (Reverted edits by Ejumuvo (Talk) to last revision by 75.172.121.11) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
= (R)DEPENDS, etc. = | = (R)DEPENDS, etc. = | ||
libiconv in (R)DEPENDS | |||
: Use "virtual/libiconv" instead as glibc based systems already have libiconv functionality from glibc. Uclibc based systems will get it from "libiconv". By building libiconv in glibc build You risk a corrupted TMPDIR which will need to be restarted from scratch. | |||
kernel modules in RDEPENDS | |||
: Never use RDEPENDS to drag kernel modules into an image, use RRECOMMENDS instead. The reason is that some devices can have those modules built-in into kernel. | |||
[[Category:Dev]] | [[Category:Dev]] | ||
[[Category:FAQ]] | [[Category:FAQ]] | ||
Latest revision as of 09:41, 24 November 2010
This page should list common (!) mistakes when defining a recipe. a link or one sentence explaining what the problem is are a bonus. But keep it short!
(R)DEPENDS, etc.
libiconv in (R)DEPENDS
- Use "virtual/libiconv" instead as glibc based systems already have libiconv functionality from glibc. Uclibc based systems will get it from "libiconv". By building libiconv in glibc build You risk a corrupted TMPDIR which will need to be restarted from scratch.
kernel modules in RDEPENDS
- Never use RDEPENDS to drag kernel modules into an image, use RRECOMMENDS instead. The reason is that some devices can have those modules built-in into kernel.