Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 3593 - xfree-4.2.0-r12 ebuild fails
Summary: xfree-4.2.0-r12 ebuild fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Martin Schlemmer (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-10 14:34 UTC by Ryan Dooley
Modified: 2003-02-04 19:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Dooley 2002-06-10 14:34:56 UTC
In an upgrade from 1.1a to 1.2, xfree-4.2.0-r12 fails to install with:

cp: `XftConfig`: Argument list too long

from /var/tmp/portage/xfree-4.2.0-r12/work/xc/lib/Xft

Function src_install, Line 9, Exitcode 2
Comment 1 Ryan Dooley 2002-06-11 12:02:33 UTC
More... moving into /var/tmp/portage/xfree-4.2.0-12/work/xc/lib/Xft

Doing a simple ``make install" shows that

+ install -c -m 0444 XftConfig /usr/X11R6/lib/X11/XftConfig
cp: `XftConfig': Argument list too long

Intresting enough, a second ``make install" gives

Not overwriting existing /usr/X11R6/lib/X11/XftConfig
cp: `XftCofnfig': Argument list too long


Comment 2 Ryan Dooley 2002-06-12 09:49:11 UTC
Ok, I built 4.2.0-r12 on another machine with the --buildpkg option to emerge. 
The wierd thing is that both of these machines are in sync with one another and
I had expected the build to fail but it didn't.  I moved the package over to the
machine having the build problems and installed the tar.bz2 there.

Comment 3 Martin Schlemmer (RETIRED) gentoo-dev 2002-06-17 13:42:11 UTC
Sorry, forgot to reply before I went away for the weekend.  This seems like
another case which is caused when you merge fileutils with "acl" in your
USE.  Check that you dont have it in USE, or merge by doing:

# USE="-acl" emerge fileutiles

And then try Xfree again.

As for a fix for this ... Ill have to look into it.
Comment 4 Ryan Dooley 2002-06-17 15:31:16 UTC
Argh! :-)

Thanks Martin.  That was it.  Turns out I missed it in my USE="" line.  I must
be blind.