On Thu, Jan 30, 2014 at 01:08:13AM -0500, Adam Jensen wrote:
Hi,
I installed the gnat-4.8 package and I noticed that all of the executables
were prefixed with an e, e.g. egcc, egnat, egnatmake, etc. This introduces
some awkwardness into building other software. Is there a good reason to
It would cause problems. If the software you're building doesn't support
setting compiler names via environment variables to a configure script or via
overriding variables on the make command line (as most do), the simplest option
is to place symlinks in a directory (cc- usr/local/bin/egcc etc)
Thanks for the responses! Setting user aliases, environment variables, and
passing variables through *make* seem to take care of most of the issue.
However, I am currently stuck with this error (during a build):
egcc-ar: Cannot find plugin 'liblto_plugin.so'
The plugin seems to be present:
On Thu, 30 Jan 2014 19:20:37 -0500
Adam Jensen han...@riseup.net wrote:
Thanks for the responses! Setting user aliases, environment
variables, and passing variables through *make* seem to take care of
most of the issue. However, I am currently stuck with this error
(during a build):
Hi,
I installed the gnat-4.8 package and I noticed that all of the executables were
prefixed with an e, e.g. egcc, egnat, egnatmake, etc. This introduces some
awkwardness into building other software. Is there a good reason to have it
this way? Or, to put it another way, would it break
