| View previous topic :: View next topic |
| Author |
Message |
DiskDoc
Apprentice
Joined: 25 Apr 2002
Posts: 196
Location: Finland
|
 Posted: Mon Oct 21, 2002 2:13 pm Post subject: Emerge symlink problem |
 |
|
Here's a sneaky one.. I've tried upgrading a Gentoo 1.2 box to 1.4 but somewhere along the line I must have screwed something up.
It seems emerge can't create symlinks anymore. For example, the command "emerge" doesn't work anymore after re-emerging Portage because there is no symlink to /usr/lib/portage/emerge in /usr/bin! Seems autoconf and aclocal+others are complaining as well. Compiling gave me some headaches last night when binutils had the same problem - no symlinks to as & co. in the /usr/bin directory. I made a quickfix and did the symlinks myself but I can't do that everytime I update something!
Emerge seems to do everything it should...or?
| Code: |
...
--- !mtime obj /usr/lib/portage/bin/tbz2tool
--- !mtime obj /usr/lib/portage/bin/sandbox
--- !mtime obj /usr/lib/portage/bin/repoman
--- !mtime obj /usr/lib/portage/bin/quickpkg
--- !mtime obj /usr/lib/portage/bin/queryhost.sh
--- !mtime obj /usr/lib/portage/bin/prepstrip
--- !mtime obj /usr/lib/portage/bin/prepman
--- !mtime obj /usr/lib/portage/bin/preplib.so
--- !mtime obj /usr/lib/portage/bin/preplib
--- !mtime obj /usr/lib/portage/bin/prepinfo
--- !mtime obj /usr/lib/portage/bin/prepallstrip
--- !mtime obj /usr/lib/portage/bin/prepallman
--- !mtime obj /usr/lib/portage/bin/prepallinfo
--- !mtime obj /usr/lib/portage/bin/prepalldocs
--- !mtime obj /usr/lib/portage/bin/prepall
--- !mtime obj /usr/lib/portage/bin/pkgname
--- !mtime obj /usr/lib/portage/bin/pkgmerge.new
--- !mtime obj /usr/lib/portage/bin/pkgmerge
--- !mtime obj /usr/lib/portage/bin/pkglist
--- !mtime obj /usr/lib/portage/bin/pdb.cgi
--- !mtime obj /usr/lib/portage/bin/pdb
--- !mtime obj /usr/lib/portage/bin/newsbin
--- !mtime obj /usr/lib/portage/bin/newman
--- !mtime obj /usr/lib/portage/bin/newlib.so
--- !mtime obj /usr/lib/portage/bin/newlib.a
--- !mtime obj /usr/lib/portage/bin/newins
--- !mtime obj /usr/lib/portage/bin/newexe
--- !mtime obj /usr/lib/portage/bin/newdoc
--- !mtime obj /usr/lib/portage/bin/newbin
--- !mtime obj /usr/lib/portage/bin/fperms
--- !mtime obj /usr/lib/portage/bin/fowners
--- !mtime obj /usr/lib/portage/bin/find-requires
--- !mtime obj /usr/lib/portage/bin/find-packages
--- !mtime obj /usr/lib/portage/bin/etc-update
--- !mtime obj /usr/lib/portage/bin/env-update
--- !mtime obj /usr/lib/portage/bin/emerge
--- !mtime obj /usr/lib/portage/bin/emake
--- !mtime obj /usr/lib/portage/bin/ebuild.sh~
--- !mtime obj /usr/lib/portage/bin/ebuild.sh
--- !mtime obj /usr/lib/portage/bin/ebuild
--- !mtime obj /usr/lib/portage/bin/dosym
--- !mtime obj /usr/lib/portage/bin/dosed
--- !mtime obj /usr/lib/portage/bin/dosbin
--- !mtime obj /usr/lib/portage/bin/dopython
--- !mtime obj /usr/lib/portage/bin/domo
--- !mtime obj /usr/lib/portage/bin/doman
--- !mtime obj /usr/lib/portage/bin/dolib.so
--- !mtime obj /usr/lib/portage/bin/dolib.a
--- !mtime obj /usr/lib/portage/bin/dolib
--- !mtime obj /usr/lib/portage/bin/dojar
--- !mtime obj /usr/lib/portage/bin/doins
--- !mtime obj /usr/lib/portage/bin/doinfo
--- !mtime obj /usr/lib/portage/bin/dohtml
--- !mtime obj /usr/lib/portage/bin/dohard
--- !mtime obj /usr/lib/portage/bin/doexe
--- !mtime obj /usr/lib/portage/bin/dodoc
--- !mtime obj /usr/lib/portage/bin/dodir
--- !mtime obj /usr/lib/portage/bin/dobin
--- !mtime obj /usr/lib/portage/bin/db-update.py
--- !mtime obj /usr/lib/portage/bin/chkcontents
--- !mtime obj /lib/libsandbox.so
<<< sym /usr/bin/xpak
<<< sym /usr/bin/tbz2tool
<<< sym /usr/bin/repoman
<<< sym /usr/bin/emerge
--- !empty dir /var/tmp
--- !empty dir /var
--- !empty dir /usr/share/man/man5
--- !empty dir /usr/share/man/man1
--- !empty dir /usr/share/man
--- !empty dir /usr/share/doc/portage-2.0.38
--- !empty dir /usr/share/doc
--- !empty dir /usr/share
--- !empty dir /usr/sbin
--- !empty dir /usr/lib/python2.2/site-packages
--- !empty dir /usr/lib/python2.2
--- !empty dir /usr/lib/portage/lib
--- !empty dir /usr/lib/portage/bin
--- !empty dir /usr/lib/portage
--- !empty dir /usr/lib
--- !empty dir /usr/bin
--- !empty dir /usr
--- !empty dir /lib
--- !empty dir /etc
--- !targe sym /usr/sbin/pkgmerge
--- !targe sym /usr/sbin/etc-update
--- !targe sym /usr/sbin/env-update
--- !targe sym /usr/sbin/ebuild.sh
--- !targe sym /usr/sbin/ebuild
--- !targe sym /usr/lib/portage/bin/pmake
--- !targe sym /usr/lib/portage/bin/donewins
>>> original instance of package unmerged safely.
* WARNING: The default behavior for 'emerge rsync' is to have --clean enabled.
* Please back up any modified files in your Portage tree before running emerge
* rsync.
* You may want to move any custom ebuilds to a new directory, and then set
* PORTDIR_OVERLAY (in /etc/make.conf) to point to this directory. For example,
* make a /usr/portage.local/sys-apps/foo directory and put your ebuild in there.
* Then set PORTDIR_OVERLAY="/usr/portage.local" Portage should see your
* personal ebuilds. NOTE: PORTDIR_OVERLAY support is *beta* code; it may not
* work correctly yet.
>>> Regenerating /etc/ld.so.cache...
>>> sys-apps/portage-2.0.38 merged.
* GNU info directory index is up-to-date.
* IMPORTANT: 31 config files in /etc need updating.
* Type emerge --help config to learn how to update config files.
|
|
|
| Back to top |
|
 |
DiskDoc
Apprentice
Joined: 25 Apr 2002
Posts: 196
Location: Finland
|
| Posted: Mon Oct 21, 2002 2:35 pm Post subject: emerge -debug |
|
|
I tried doing emerge -d portage but the symlinking looks alright..straaange.
| Code: |
+ dodir /usr/bin /usr/sbin
+ dosym ../lib/portage/bin/emerge /usr/bin/emerge
+ dosym ../lib/portage/bin/pkgmerge /usr/sbin/pkgmerge
+ dosym ../lib/portage/bin/ebuild /usr/sbin/ebuild
+ dosym ../lib/portage/bin/ebuild.sh /usr/sbin/ebuild.sh
+ dosym ../lib/portage/bin/etc-update /usr/sbin/etc-update
+ dosym ../lib/portage/bin/env-update /usr/sbin/env-update
+ dosym ../lib/portage/bin/xpak /usr/bin/xpak
+ dosym ../lib/portage/bin/repoman /usr/bin/repoman
+ dosym ../lib/portage/bin/tbz2tool /usr/bin/tbz2tool
+ dosym newins /usr/lib/portage/bin/donewins
|
|
|
| Back to top |
|
|
DiskDoc
Apprentice
Joined: 25 Apr 2002
Posts: 196
Location: Finland
|
| Posted: Mon Oct 21, 2002 2:39 pm Post subject: Solution |
|
|
| Hm, I think I got it! I have portage on a different drive/filesystem. Symlinks doesn't work across..different...filesystems? |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Mon Oct 21, 2002 6:28 pm Post subject: Re: Solution |
|
|
| DiskDoc wrote: | | Hm, I think I got it! I have portage on a different drive/filesystem. Symlinks doesn't work across..different...filesystems? |
They should. You said that making the symlinks manually worked, so maybe this isn't the case, but what does mount say about your partition types? Is there a chance that one of them is mounted as vfat? I have symlinks that cross filesystems. For example, my /var is a separate partition, and I put home on there. I have a symlink /home to /var/home, which sits on the root partition, and it works fine. I also just tried making a deeper one to /usr/bin/less from /var/tmp/less, and that worked fine too.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
n0n
Guru
Joined: 13 Jun 2002
Posts: 355
|
| Posted: Tue Oct 22, 2002 2:30 am Post subject: |
|
|
| Yeah, symlinks will work fine across filesystems, though obviously not on filesystems that don't support symlinks. It's hard links that won't work across filesystems, because of the way they're stored. A symlink says "the file you want is really located /over/here", whereas a hardlink just points right at the file's data as if it was the sole owner of the file. 'fraid that I'm stumped as to how to fix your problem, though. |
|
| Back to top |
|
|
|
Installing Gentoo
