Emerging xorg-server fails

[theamazingplant2]

Hello.
I have been using gentoo for about two weeks now, and after various partitioning mishaps, my gentoo was lost
so, i have been trying to rebuild it from scratch again- and not doing very well.
i have just got done compiling the kernel, and am now on the part where you get the xorg-server working. so i did emerge xorg-server --autounmask-write, and it wrote the changes, and then i ran etc-update to update it.
after all this, i did emerge xorg-server again, and i got this error from portage during the installation of about the third dependencie of about 109 of them:rm: cannot remove `/var/tmp/portage/sys-devel/bison-2.4.3/image//usr/lib/liby.a': Bad file descriptor
* ERROR: sys-devel/bison-2.4.3 failed (install phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 85: Called src_install
* environment, line 2105: Called die
* The specific snippet of code:
* rm -r "${D}"/usr/lib* || die;
*
* If you need support, post the output of 'emerge --info =sys-devel/bison-2.4.3',
* the complete build log and the output of 'emerge -pqv =sys-devel/bison-2.4.3'.
* The complete build log is located at '/var/tmp/portage/sys-devel/bison-2.4.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/bison-2.4.3/temp/environment'.
* S: '/var/tmp/portage/sys-devel/bison-2.4.3/work/bison-2.4.3'

>>> Failed to emerge sys-devel/bison-2.4.3, Log file:

>>> '/var/tmp/portage/sys-devel/bison-2.4.3/temp/build.log'

* Messages for package sys-devel/bison-2.4.3:

* ERROR: sys-devel/bison-2.4.3 failed (install phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 85: Called src_install
* environment, line 2105: Called die
* The specific snippet of code:
* rm -r "${D}"/usr/lib* || die;
*
* If you need support, post the output of 'emerge --info =sys-devel/bison-2.4.3',
* the complete build log and the output of 'emerge -pqv =sys-devel/bison-2.4.3'.
* The complete build log is located at '/var/tmp/portage/sys-devel/bison-2.4.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/bison-2.4.3/temp/environment'.
* S: '/var/tmp/portage/sys-devel/bison-2.4.3/work/bison-2.4.3'

if you need any more info, please let me know. i would really love to get X running again just like i did before. if it helps, i am chrooting into the enviroment using ubuntu.

[NeddySeagoon]

theamazingplant2,

Its really hard to destroy gentoo with partition mishaps. You might not know where it is for a while but its still there.
You just can't find it is all.

When things fail to build, we need the complete build log, which in this case is

[gorkypl]

[theamazingplant2]

thanks gorkypl, i just realized that i did NOT have /dev mounted. thanks for answering.
ps:
neddyseagon: I did in fact accidentally delete the whole partition, so it is gone. I finally got it to build, but thanks for answering. and i didnt know that i shouldnt do the --autounmask-write.
( im still kinda new to the whole gentoo thing, and while i was a power user there, i kinda still need to get my bearings on gentoo)

[NeddySeagoon]

theamazingplant2,

There is deleting a partition and deleteing a partition.

Going into fdisk and deleting a partition only deletes the partition table entry in the partition table. Your data in the partition is safe and sound unless you make a new partition using the old space then make a filesystem in the new partition. If you delete a partition with fdisk, then think "oops". Your data is still all there - you have just deleted the pointers that allow the kernel to locate the filesystem.

Its a more common occurance than you might think and there are tools to help you recover.

Getting you data back after you have mad a new filesystem is much harder - a reinstall will be faster.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.