https://sourceware.org/bugzilla/show_bug.cgi?id=32271
--- Comment #6 from Nick Clifton <nickc at redhat dot com> --- (In reply to Stas Sergeev from comment #5) > Even if it covers some "random" > data in a file? IMHO that's still > a but. If it would be zero-sized > then fine. But its not. Can you provide a small example that reproduces this please ? It looks like something that needs to be investigated. > > Have you tried linking with -Ttext=0xNNNNNNNN ? (And/or --text-segment=X > > --rodata-segment=X --ldata-segment=X). > > Just tried, and wtf? > $ x86_64-linux-gnu-ld int23.o int0.o asm.o ms.o plt.o -melf_i386 -static > /usr/local/i386-pc-dj64/lib/uplt.o --text-segment=0x08148000 -o tmp.elf > x86_64-linux-gnu-ld: unrecognized option '--text-segment=0x08148000' > x86_64-linux-gnu-ld: use the --help option for usage information My bad. The option is -Ttext-segment=... rather than --text-segment=... Sorry. > Wow, so lets try this then: > $ x86_64-linux-gnu-ld int23.o int0.o asm.o ms.o plt.o -melf_i386 -static > /usr/local/i386-pc-dj64/lib/uplt.o -text-segment=0x08148000 -o tmp.elf > x86_64-linux-gnu-ld: Error: unable to disambiguate: -text-segment=0x08148000 > (did you mean --text-segment=0x08148000 ?) > > Now it hints me to use -text-segment=0x08148000 > only to declare it "unrecognized option"? > Very funny. :) Yeah - the algorithm for hinting at spelling mistake corrections is not that smart... -- You are receiving this mail because: You are on the CC list for the bug.
