Created attachment 395570 [details] libstdc++.so.6.0.20-gdb.py The message is libstdc++.so.6.0.20-gdb.py is not an elf file it has the wrong magic bytes at the start
It isn't entirely clear what you are trying to do, what the attachment is supposed to do and where the attachment comes from.
(In reply to Jeroen Roovers from comment #1) > It isn't entirely clear what you are trying to do, what the attachment is > supposed to do and where the attachment comes from. the file resides in /usr/lib. and the message received after updating gcc was as stated. It does not appear to be creating any hassles so far,but thought it strange that I would receive the error message. As an addition I ran python-updater.and the message has not appeared since.
Please post the command you used that triggered this bug report, as well as its entire output.
emerge -uaND @world,this updated gcc-4.8.4 to 4.9.2. Now when I do an update I get the message as reported initially.
(In reply to Geoff Madden from comment #0) > Created attachment 395570 [details] > libstdc++.so.6.0.20-gdb.py > > The message is "libstdc++.so.6.0.20-gdb.py is not an elf file - it has the > wrong magic bytes at the start"
(In reply to Geoff Madden from comment #5) > (In reply to Geoff Madden from comment #0) > > Created attachment 395570 [details] > > libstdc++.so.6.0.20-gdb.py > > > > The message is "libstdc++.so.6.0.20-gdb.py is not an elf file - it has the > > wrong magic bytes at the start" This is still the case,.even after python update. when I call the update procedure & the particular file is being configured( any one in this case),the message keeps repeating. throughout this procedure.
Comment on attachment 395570 [details] libstdc++.so.6.0.20-gdb.py What reports that? If this happens during an emerge run, then attach the entire build log (and not the file, since everyone who installs sys-devel/gcc-4.9.* gets the file anyway).
> Why ldconfig complains please? Because it assumes all files in /usr/lib are ELF files, and that file is not. You can safely ignore it.
(In reply to Jeroen Roovers from comment #8) > > Why ldconfig complains please? > > Because it assumes all files in /usr/lib are ELF files, and that file is not. > > You can safely ignore it. OK thanks for the reply,I half figured that might be the case,but thought to report just in case
what version of gcc is installing that ? please post the full build log for that version of gcc as well as your emerge info. gcc should not be installing any of the gdb python helpers into libdir paths (nor is it doing that on my systems).
(In reply to SpanKY from comment #10) > what version of gcc is installing that ? please post the full build log for > that version of gcc as well as your emerge info. gcc should not be > installing any of the gdb python helpers into libdir paths (nor is it doing > that on my systems). Not too sure,as to the build log that has been expunged,when the gcc build completed successfully. I am beginning to think this file may have been deposited from a previous install of gdb,which was subsequently removed,after a time of not needing it. As to the reported mismatch,gcc-4.8.4 did not report on configuration,it's only since the update to 4.9.2 the report has manifested. Also I'm not actually using that machine at present,it has been parked till I get the rest of my systems updated.
