Thank you. That worked. The only modification I had to make was to make the string for config TOOLCHAIN_CFLAGS empty otherwise the LTIB configure menu showed two items for CFLAGS for my custom toolchain.

On 3/28/16, 11:12 AM, Peter Barada wrote:
Hmm, I don't have a universe to run with right now (out of town with
only my laptop), but I see in config/userspace/toolchain.lkc that
there's a CUSTOM_TOOLCHAIN_PREFIX as well as TOOLCHAIN_PREFIX which
defaults to CUSTOM_TOOLCHAIN_PREFIX if CUSTOM_TOOLCHAIN=y.  However
there's not corresponding CUSTOM_TOOLCHAIN_CFLAGS.

Attached is a patch to the current CVS version (Version 1.7) of
config/userspace/toolchain.lkc that adds it.  I haven't built with this
change (so your mileage _will_ vary), but see if the patch fixes the
issue.  You'll want to apply the patch, run ltib -c to setup your custom
toolchain flags, then save/exit, retry ltib -c and inspect to see if
TOOLCHAIN_CFLAGS is no longer empty.

Hope this helps!


On 03/25/2016 04:14 PM, Josh Pagnotta wrote:
Hi,

We have modified our LTIB config to use a custom toolchain and now
whenever we open the LTIB configuration menu (ltib -c), the
TOOLCHAIN_CFLAGS are empty and we have to enter them in again. When we
save the config they are there, but when we load it again they are
gone, making us think the issue is on the loading of the config.

Thanks

_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib


_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib

_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib

Reply via email to