First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 150257
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Toolchain Maintainers <toolchain@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Diego Pettenò <flameeyes@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
gcc-config-patch gcc-config-patch patch Diego Pettenò 2006-10-06 05:34 0000 1.35 KB Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 150257 depends on: Show dependency tree
Show dependency graph
Bug 150257 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-10-06 05:33 0000 
As per summary, currently the way to update libgcc_s.so.1 make impossible for
catalyst to update the gcc profile the first time when the linker does not know
to look into gcc's own directories and libgcc_s.so.1 is needed by the mv
command.

${MV} -f "${ROOT}/${libdir}"/.gcc.config.new/* "${ROOT}/${libdir}"/

will fail if mv tries to load the just-removed libgcc_s.so.1 library.
This affects Gentoo/FreeBSD but might affect also Gentoo Linux on some
architectures.

The attached patch makes sure that a copy of libgcc_s.so.1 is always found in
the process.

Thanks,
Diego

------- Comment #1 From Diego Pettenò 2006-10-06 05:34:15 0000 ------- 
Created an attachment (id=98931) [edit]
gcc-config-patch

------- Comment #2 From SpanKY 2006-10-06 13:04:07 0000 ------- 
catalyst should be running gcc-config automatically on $ROOT so stage1 should
have libgcc_s.so.1 in the proper place

------- Comment #3 From Chris Gianelloni 2006-10-11 06:02:24 0000 ------- 
I'll look at what catalyst is doing once we've gotten it moved to SVN, which is
going on now.

------- Comment #4 From Roy Marples (RETIRED) 2006-10-15 08:37:34 0000 ------- 
I'm not sure this is a catalyst issue as I ran into the same thing just doing

ROOT=/stage3 emerge -e system
Diegos patch fixes this on my Gentoo/FreeBSD/Sparc64 :)

------- Comment #5 From SpanKY 2006-10-18 21:01:23 0000 ------- 
fixed in cvs by not removing the file anymore; let the `mv` handle it
First Last Prev Next    No search results available      Search page      Enter new bug