Messages in this thread | | | From | Andreas Schwab <> | Subject | Re: discarded `.exit.text' debugging? | Date | Tue, 21 Oct 2008 00:01:39 +0200 |
| |
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> Last night I got these in my build logs: > > | `.exit.text' referenced in section `.init.text' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o > | `.exit.text' referenced in section `.data' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o > > i.e. not much context. Is there an easy way to find out who's the > offender?
You could try giving each .exit.text section a unique name per object file (so that "ld -r" does not merge them) and modify EXIT_TEXT to collect all those sections during the final link.
Andreas.
-- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |