| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Run ./bootstrap on the configure commands, otherwise it will be run
again by the build tool but this time without the right arguments. This
would result in a build failure.
Change-Id: Ib93e5398229fa9f2fc00bfcd74a502553e5f92d6
|
|
|
|
|
|
|
|
|
|
|
|
| |
This actually revert some changes we made a while back (74ce6a18, 7cb71771,
7c2bfac9)
I realize we will have to patch a lot of modules manually following this route.
Also, I remember to see some commands from chunks that, even they build fine,
they will show UNKNOWN if you type <command> --version
Basically the chunks assume that if you are building from git, you have git
installed
Change-Id: I886288553e8edf05ffc1cb497fabbadb468819b7
|
|
|
|
| |
Change-Id: Idd1a0c155f2872c2b4aba64fa388e505e04fe7ab
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit c5240343053398d288cc500ff54379a3b0de5309.
The original clean-up patch breaks the native build phase of
cross-bootstrap on tested platforms - armv8l64, armv8b64, and
x86_64.
In the bootstrap environment, the native build of bison does
rely on being run with bash rather than sh.
Change-Id: Id8ed8793f8a179615a2f8733e867445cac544043
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The version number of bison appends a part of the sha1
of the commit which is being built. This was causing
failures in the autoconf when building gstreamer given
that it tries to compare the version number of bison.
This is a *workaround* to generate a clean version number
of bison.
Notes:
Author: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
|
|
|