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 14:39:17 +0300 > > > Note that additional "-Tdjgpp-x.djl" at the end which screws up everything. > > > > What if you use both -T and -Xlinker -T? IOW, pass -T both to GCC and > > to the linker directly? > > That works with gcc-3.4.6, but not with gcc-2.95: adding -v to command line > shows that gcc295 invokes ld with -Tdjgpp.djl -T dxe.ld > > > If this still doesn't work, can you show the output of "gcc -dumpspecs" > > from GCC 2.95? > > Attached as 295SPECS.TXT [EDIT: really attached it this time.] OK, I see the problem now. So this means people who use GCC 2.95 will have to use the previous version of dxe3gen. In that case, I think I'm okay with documenting this and ignoring the problem with GCC 2.95. > >>> OK, but still: there should be no problem with having both on the > >>> command line, right? > >> > >> No, no problems. But detecting and correctly using -lgcc was the > >> original goal. > > > > But -L doesn't contradict that goal, does it? > > I'm trying to understand your question and how you see things: > What I'm saying is, needing to add an additional -L/some/path for > -lgcc is really counter-intuitive and unexpected. I guess someone > has to run gcc -print-libgcc-file-name to manually detect it and > than add it to his own command line. Sure, but we are already talking about someone who does something very non-standard. I just prefer that we leave those hypothetical people a way of keeping their setups, whatever they are, and I think supporting DJDIR and DXE_LD_LIBRARY_PATH for adding -L options to the command line cannot do any harm to people who use the standard directories, right?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |