Summary: | ldconfig with ROOT across archs breaks cache | ||
---|---|---|---|
Product: | Portage Development | Reporter: | James Le Cuirot <chewi> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=532100 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 181949, 187293 | ||
Attachments: | run \${CHOST}-ldconfig when \${CBUILD} != \${CHOST} |
Description
James Le Cuirot
2006-10-25 17:16:50 UTC
it isnt really architecture dependent ... it does have endian issues though which is probably what you're seeing (i imagine your host is little endian x86/amd64 while the target is big endian ppc) Yeah I thought it might be that. I can't think of any simple way to check the endianness of both / and ROOT though. Hmmm... Mike, Ned: any suggestion how to fix this? I have retired that PPC machine now but I still have my big endian m68k Amiga 1200 sitting right here. (-; A solution would be appreciated. we should test the env to see if it's a cross-compiler ... LDCONFIG="ldconfig" if [[ ${CBUILD} != ${CHOST} ]] ; then LDCONFIG="${CHOST}-ldconfig" fi if type -P ${LDCONFIG} > /dev/null ; then <actually run ldconfig> fi Created attachment 121536 [details, diff]
run \${CHOST}-ldconfig when \${CBUILD} != \${CHOST}
This should do it.
This has been released in 2.1.2.10. |