Opened 17 years ago

Closed 17 years ago

#1065 closed bug (invalid)

elf_resolve_symbol: could not resolve symbol 'memset_internal'

Reported by: rdaneel Owned by: axeld
Priority: normal Milestone: R1
Component: System/runtime_loader Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

After copy and link files from a CD, i have this message when i tried to use 'ls', 'cp' or 'mv' (not 'help', por example):

elf_resolve_symbol: could not resolve symbol 'memset_internal' resolve_symbol "memset_internal" return: -2147478780 runtime_loader: troubles relocating: 0x80001304

Tested in VmWare (rev: 20288).

PD: AboutHaiku is failing with the same error.

Change History (4)

comment:1 by axeld, 17 years ago

Can you please provide a list of the files you copied? You may have accidently replaced a system library.

comment:2 by rdaneel, 17 years ago

I just linked /beos/system/lib (from Beos Max) to /Haiku/home/config/lib (its empty) . I didnt replace any system library.

comment:3 by korli, 17 years ago

Maybe it could be good to search for lib first in beos/system/lib and then in home/config/lib :)

comment:4 by axeld, 17 years ago

Resolution: invalid
Status: newclosed

I don't know, it would be some kind of user protection, but it *sometimes* isn't what you would want to do, and might tempt you to replace a system lib physically as well. Maybe it's less of a problem if the system you're using is actively maintained, though, and therefore your libs are reasonably up to date.

Another option would be to ignore user library paths when starting system applications. I think I would like that a lot.

Anyway, I'm closing this bug, as it's invalid: since home/config/lib/ supersedes /system/lib/ (by intention, not accidently), every library you put into the former with a name that exists in the latter will replace the latter library. Therefore, Haiku suddenly tries to use BeOS MAX libs which aren't compatible.

Note: See TracTickets for help on using tickets.