| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding the SDKTAROPTS can result in either a failure or an endless loop when
generating the SDK tarball. This is due to potential recursive symlinks
within the cross compiler directory structure.
It also means files from places /var/log on the build system can be pulled
into the sdk, dependning on the chosen rootfs of the target system this
is built against.
Disabling it is therefore the best opton, when post processing the tarball,
the symlinks can be dealt with accordingly but the current approach is just
dangerous.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
The symlinking is really an artefact of the way the headers are
provided. Move all the code into one place.
Also have the initial compiler depend on the headers else the build
can fail. High parallelism prevented the issue from being seen
in most cases.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
| |
The compiler flags were not getting passed to the compiler, this fixes
the make command so they do get preserved.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
