Displaying 4 results from an estimated 4 matches for "17f96764".
Did you mean:
179674
2015 Sep 14
2
[PATCH] Dont bypass compiler driver for Dependency generation options
...that are only appropriate during development; this file is
>> # removed when tarballs are generated.
>
> It looks like these were introduced in MCONFIG back in commit ID
> fe938522 and originally in a bunch of other commits like fbfc9121 and
> the earliest instance appears to be 17f96764.
>
> Khem, at first I didn't quite understand the part about other
> compilers then it struck me that you're probably trying to build
> linux/syslinux and extlinux/extlinux without a gcc dependence.
I was using clang to compile it :). than I ran into further issues which I am...
2015 Sep 10
3
[PATCH] Dont bypass compiler driver for Dependency generation options
We can let compiler driver pass the right options to preprocessor after
processing -Mxy options, right now its bypassing the gcc driver and
handing them straight to cpp
This also helps in other compilers processing these options correctly
for their preprocessors consumption
Signed-off-by: Khem Raj <raj.khem at gmail.com>
---
mk/syslinux.mk | 4 ++--
1 file changed, 2 insertions(+), 2
2015 Sep 13
0
[PATCH] Dont bypass compiler driver for Dependency generation options
...-MMD
>
> # Items that are only appropriate during development; this file is
> # removed when tarballs are generated.
It looks like these were introduced in MCONFIG back in commit ID
fe938522 and originally in a bunch of other commits like fbfc9121 and
the earliest instance appears to be 17f96764.
Khem, at first I didn't quite understand the part about other
compilers then it struck me that you're probably trying to build
linux/syslinux and extlinux/extlinux without a gcc dependence.
HPA, any clue on the history of these gcc flags? Was gcc previously
error-prone on direct depende...
2015 Dec 10
0
[PATCH] Dont bypass compiler driver for Dependency generation options
...opriate during development; this file is
>>> # removed when tarballs are generated.
>>
>> It looks like these were introduced in MCONFIG back in commit ID
>> fe938522 and originally in a bunch of other commits like fbfc9121 and
>> the earliest instance appears to be 17f96764.
>>
>> Khem, at first I didn't quite understand the part about other
>> compilers then it struck me that you're probably trying to build
>> linux/syslinux and extlinux/extlinux without a gcc dependence.
>
> I was using clang to compile it :). than I ran into fu...