View previous topic :: View next topic |
Author |
Message |
mjs Tux's lil' helper
Joined: 07 Mar 2007 Posts: 91 Location: Dallas, TX.
|
Posted: Tue Apr 01, 2008 4:48 pm Post subject: emerge libstdc++-v3-bin-3.3.6 failing |
|
|
I've unmasked libstdc++-v3-bin-3.3.6, but it fails with the following errors:
>>> Install libstdc++-v3-bin-3.3.6 into /var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/image/ category sys-libs
cp: cannot stat `/var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/work/*': No such file or directory
*
* ERROR: sys-libs/libstdc++-v3-bin-3.3.6 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 82: Called die
* The specific snippet of code:
* cp -pPR "${WORKDIR}"/* "${D}"/ || die "copying files failed!"
* The die message:
* copying files failed!
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/temp/environment'.
*
* Messages for package sys-libs/libstdc++-v3-bin-3.3.6:
*
* ERROR: sys-libs/libstdc++-v3-bin-3.3.6 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 82: Called die
* The specific snippet of code:
* cp -pPR "${WORKDIR}"/* "${D}"/ || die "copying files failed!"
* The die message:
* copying files failed!
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/temp/environment'.
*
Any ideas?
I've verified that this path does exist: "/var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/work/" |
|
Back to top |
|
|
guruvan Tux's lil' helper
Joined: 21 Aug 2007 Posts: 132
|
Posted: Tue Apr 01, 2008 5:57 pm Post subject: |
|
|
Just for fun I slapped this out too. Result the same... More info at the end.....
There nada in that directory.
(furthermore, isn't that supposed to be a binary with the -bin ???? I had to wait for the thing to compile)
Code: |
* Messages for package sys-libs/libstdc++-v3-bin-3.3.6 merged to /var/tmp/BUILD-testing/:
*
* ERROR: sys-libs/libstdc++-v3-bin-3.3.6 failed.
* Call stack:
* ebuild.sh, line 46: Called src_install
* environment, line 103: Called die
* The specific snippet of code:
* cp -pPR "${WORKDIR}"/* "${D}"/ || diefunc "$FUNCNAME" "$LINENO" "$?" "copying files failed!"
* The die message:
* copying files failed!
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/temp/environment'.
*
* Regenerating GNU info directory index...
* Processed 14 info files.
xoom tmp # ls -la /var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/
.compiled .exit_status .tested .unpacked build-info/ distdir/ homedir/ image/ temp/ work/
xoom tmp # ls -la /var/tmp/portage/sys-libs/libstdc++-v3-bin-3.3.6/work/
total 0
drwx------ 2 root root 6 Apr 1 11:28 .
drwxrwxr-x 8 portage portage 150 Apr 1 11:28 ..
xoom tmp # |
_________________ Everything is broken......(b.dylan).
guruvan |
|
Back to top |
|
|
mjs Tux's lil' helper
Joined: 07 Mar 2007 Posts: 91 Location: Dallas, TX.
|
Posted: Tue Apr 01, 2008 6:29 pm Post subject: |
|
|
Yeah, the directory exists, but is empty. I don't think it actually compiled anything from what I could see. I think it's supposed to just extract and copy, but there's nothing to copy. |
|
Back to top |
|
|
Carsomyr n00b
Joined: 24 Mar 2008 Posts: 36 Location: Pretoria, South-Africa
|
Posted: Tue Apr 01, 2008 6:56 pm Post subject: |
|
|
Perhaps it is masked for a reason?
Why not just compile the normal package, which is not masked? |
|
Back to top |
|
|
guruvan Tux's lil' helper
Joined: 21 Aug 2007 Posts: 132
|
Posted: Tue Apr 01, 2008 7:06 pm Post subject: |
|
|
it's masked by arch - not hard masked. (but a good question, why not just build it.
(wasn't thinking, of course the deps weren't satisfied in my testbed - those compiled.) _________________ Everything is broken......(b.dylan).
guruvan |
|
Back to top |
|
|
mjs Tux's lil' helper
Joined: 07 Mar 2007 Posts: 91 Location: Dallas, TX.
|
Posted: Tue Apr 01, 2008 7:11 pm Post subject: |
|
|
guruvan wrote: | it's masked by arch - not hard masked. (but a good question, why not just build it.
(wasn't thinking, of course the deps weren't satisfied in my testbed - those compiled.) |
I thought of that, but I was hoping for a quick fix. I guess I'll have to see if I can find the source. With my luck, I'm sure it will break something, which is why I like to stick with ebuilds. |
|
Back to top |
|
|
Carsomyr n00b
Joined: 24 Mar 2008 Posts: 36 Location: Pretoria, South-Africa
|
Posted: Tue Apr 01, 2008 7:22 pm Post subject: |
|
|
Its masked by keyword ** (at least on x86), and not by ~x86. This means it's not supported on the architecture (I think).
As its a binary package it makes sense that theres nothing there in that case.
After unmasking it and running emerge the first time I get a download size of 0kb, which seems to indicate there is nothing there.
Just do
Code: | emerge sys-libs/libstdc++-v3 | to compile it it from the gcc sources |
|
Back to top |
|
|
mjs Tux's lil' helper
Joined: 07 Mar 2007 Posts: 91 Location: Dallas, TX.
|
Posted: Tue Apr 01, 2008 7:29 pm Post subject: |
|
|
Carsomyr wrote: | Its masked by keyword ** (at least on x86), and not by ~x86. This means it's not supported on the architecture (I think).
As its a binary package it makes sense that theres nothing there in that case.
After unmasking it and running emerge the first time I get a download size of 0kb, which seems to indicate there is nothing there.
Just do
Code: | emerge sys-libs/libstdc++-v3 | to compile it it from the gcc sources |
I just saw that. I guess I focused in on the -V3 in the name since that was the version the software specifically asked for and didn't notice the one above without the bin. Trying the libstdc++-v3 now.
Thanks |
|
Back to top |
|
|
mjs Tux's lil' helper
Joined: 07 Mar 2007 Posts: 91 Location: Dallas, TX.
|
Posted: Tue Apr 01, 2008 7:42 pm Post subject: |
|
|
Yeah, that works fine. I'm a doofus |
|
Back to top |
|
|
Carsomyr n00b
Joined: 24 Mar 2008 Posts: 36 Location: Pretoria, South-Africa
|
Posted: Tue Apr 01, 2008 8:25 pm Post subject: |
|
|
I kept trying to compile gcc-3.3.6 itself to get it. That didn't work either, so your not the only one |
|
Back to top |
|
|
guruvan Tux's lil' helper
Joined: 21 Aug 2007 Posts: 132
|
Posted: Wed Apr 02, 2008 12:38 am Post subject: |
|
|
just
emerge --oneshot libstdc++-v3
(with out the bin) and that should get you a good valid set of libraries. (it will explode the gcc-3.3.6 packge to /var/tmp/portage, and then just build what you want. _________________ Everything is broken......(b.dylan).
guruvan |
|
Back to top |
|
|
diablo465 Apprentice
Joined: 10 Sep 2013 Posts: 194
|
Posted: Mon Feb 17, 2014 3:10 pm Post subject: |
|
|
This doesn't work for me... |
|
Back to top |
|
|
|