This is the mail archive of the
mailing list for the binutils project.
Re: [RFC 0/5] xtensa: support dynamic configuration
- From: Nick Clifton <nickc at redhat dot com>
- To: Max Filippov <jcmvbkbc at gmail dot com>, binutils at sourceware dot org, gdb-patches at sourceware dot org
- Cc: Sterling Augustine <augustine dot sterling at gmail dot com>, David Weatherford <weath at cadence dot com>, Maxim Grigoriev <maxim2405 at gmail dot com>, Woody LaRue <larue at cadence dot com>
- Date: Tue, 6 Jun 2017 13:41:23 +0100
- Subject: Re: [RFC 0/5] xtensa: support dynamic configuration
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=nickc at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 03AD081247
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 03AD081247
- References: <email@example.com>
> Built toolchain takes configuration
> parameters from the shared object specified in the environment variable.
Using environment variables to pass configuration information is a bad idea.
The problem is that it can be very hard to debug problems when environment
variables are involved. Often they are not included in bug reports, which
makes reproducing the problem tricky.
At the very least you should also provide a command line option which
specifies the path to a file containing the configuration information. If
specified this option should override the environment variable.
There is also the issue of versioning to consider. Does the configuration
information contain a version number ? What happens if the configuration
information is out of date with respect to the compiler/linker or if the
tools are older than the configuration information ?