mikro wrote:When we are talking about system paths (i.e. the ones which gcc was configured with, like /usr/lib) then yes, gcc -mcpu=your_cpu is the only thing you have to care about.
But if you have a separate directory with someone else's libs, you definitely have to manually enter -L/your/custom/path/including/m68020-60 because the directory selection algorithm based on -mcpu doesn't apply here. What you provide as a search path, that is searched, period.
mikro wrote:When doing the final build, I recommend adding -Wl,-t to gcc command line, that way you will see *all* libraries and objects files linked into the executable.
ThorstenOtto wrote:So best thing is to trace the actually libraries used using one of the methods mentioned above.
Users browsing this forum: No registered users and 5 guests