On Fri, 10 Mar 2017, Daniel Santos wrote: > 3. Wouldn't it be better to move this logic up into DejaGnu and restrict gcc > to using a black-box interface for modifying the environment?
GCC is meant to work with a wide range of different DejaGnu versions. There would be a long gap between adding board-file interfaces for controlling library paths - because that's the right level, interfaces that a board file can define alongside open, close, load, exec, spawn, etc. - and being able to assume they are available. Of course you might try to arrange things so that existing board files not defining such interfaces continue to work (most custom board files are likely to be for bare metal where shared libraries don't exist) and so that GCC continues to work with versions of DejaGnu without such interfaces. Finding shared libraries is generally simpler with installed testing, in that it becomes the responsibility of the board file, site.exp and the rest of the user-provided test environment to arrange for shared libraries to be in locations where they are found automatically. -- Joseph S. Myers jos...@codesourcery.com
