www.delorie.com/archives/browse.cgi | search |
> From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com> > Date: Sat, 28 Jan 2023 00:03:33 +0300 > > >> . the code will no longer heed DXE_LD_LIBRARY_PATH and DJDIR > > > > In the vast majority of cases those would point to the global lib > > directory. > > That is no longer necessary, gcc will know where to look. > > > > In case someone used DXE_LD_LIBRARY_PATH to point to something > > else, that seems like a strange configuration, was that ever intended to > > be supported? > > That one was supposed to let ld know where the library dir is. > If anyone else actually used it for something else, well, as I said, > they can always use -L/some/path -lfoo as they always could. Why cannot we tweak the way we compute the command arguments to still honor these two variables? It's a simple matter of reusing code that was already there, and was used for ages, no? IOW, is there a real reason for removing the code which used the values of those two environment variables?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |