Portage/emerge doesn't seem to like sym link

jondkent · Apprentice Joined: 26 Jul 2002 Posts: 289 Location: London

Hiya,

Trying to upgrade the system level with

emerge -u system

however, some build such as gettext seem to baff with ACCESS VIOLATION errors. Had a look at this and it seems to be because Portage does not link symbolic links which I have in place for /usr/lib due to disk space problems. I disabled the sandbox for one build, gettext, and everything installed OK so its not the source itself.

OK I thought lets put lib back into /usr/lib proper and sym link /var/tmp/portage to my emptier partition. No joy there either, complains about the path when it tries to patch a build or create the working directory (no idea why as I can do it manually).

This looks like a bug to me within portage as it seems to take the actual path name not the relative path name, which is a bit odd.

If anyone has any ideas that would be great as I've had to call off the upgrade for the moment. Reinstalling is not a preferred option at the moment

Thanks

Jon

rac · Posted: Fri Oct 25, 2002 2:41 am Post subject:

Does explicitly setting PORTAGE_TMPDIR work better than symlinking /var/tmp/portage somewhere?
_________________
For every higher wall, there is a taller ladder

jondkent · Apprentice Joined: 26 Jul 2002 Posts: 289 Location: London

Thats interesting, I'll give that variable a try tonight.

Anyone have any ideas which sym linking /usr/lib should give Portage grief :?:

Cheers

Jon

dreamer3 · Guru Joined: 24 Sep 2002 Posts: 553

I'm not sure, but symlinks aren't 100% real... try mount --bind... cool stuff :-)

It can remount one part of the file system to another.

I use it to keep the parts of my file system that change the most on hda2.

mount except: