by nickoppen » Mon Oct 20, 2014 10:00 am
Hi Andy,
I checked that. If I do a "whoami" as a pre-build step I get the response "linaro".
Since I posted my question I did an "env" prior to the build and the environment variable LD_LIBRARY_PATH is blank. It exists but is not set to anything. However, putting it is as a custom variable causes it to be set pre-build (i.e. I can "echo LD_LIBRARY_PATH" and that works) but attempting to set an environment variable pre-build does not seem to have any effect (i.e. LD_LIBRARY_PATH="/usr/local/...."; export LD_LIBRARY_PATH; echo $LD_LIBRARY_PATH; returns the path but the error persists).
Running clcc on the command line works but as linaro you set a message that says you need to be root to compile one of the modules (e-init() I think), so I tried to run clcc via sudo but that was equally unsuccessful. Again I think that the problem is that the LD_LIBRARY_PATH is blanked out and so using the -E option to preserve the environment is no use.
I tried to run "su" as a pre-build step but that needs to be run from a command prompt.
So, no... I don't believe so.
nick
Sharing is what makes the internet Great!