1 |
Dustin Knie wrote: |
2 |
> i attempted to emerge update world a couple days ago, and it stoped at |
3 |
> hdparm with the following: |
4 |
> |
5 |
> prophet root # emerge hdparm |
6 |
> Calculating dependencies ...done! |
7 |
> |
8 |
>>>>emerge sys-apps/hdparm-4.9 to / |
9 |
>>>>md5 ;-) hdparm-4.9.tar.gz |
10 |
>>>>Unpacking source... |
11 |
>>>>Unpacking hdparm-4.9.tar.gz |
12 |
>>> |
13 |
> sed: -e expression #2, char 31: Unknown option to `s' |
14 |
> |
15 |
>>>>Source unpacked. |
16 |
>>> |
17 |
> make: *** No rule to make target `all'. Stop. |
18 |
> make: *** No rule to make target `all'. Stop. |
19 |
> |
20 |
> !!! ERROR: The ebuild did not complete successfully. |
21 |
> !!! Function src_compile, Line 1, Exitcode 2 |
22 |
> !!! (no error message) |
23 |
> |
24 |
> !!! emerge aborting on /usr/portage/sys-apps/hdparm/hdparm-4.9.ebuild . |
25 |
> prophet root # |
26 |
> |
27 |
> |
28 |
> In order to get around this, I did emerge inject hdparm-4.9 and update |
29 |
> world continued as expected. However, now im still stuck with 4.6, and |
30 |
> 4.9 is shown as installed (although it isnt...) This isnt really a |
31 |
> problem at the moment, but it may be in the future, and I would like to |
32 |
> resolve this. |
33 |
|
34 |
|
35 |
I was just having probles which manifested themselves in sed errors, but it |
36 |
turned out to be a problem in my /etc/make.conf. In particular, I had |
37 |
spread my CFLAGS onto multiple lines with a \ at the end of each line. |
38 |
Turns out that my CFLAGS were being passed to sed just like that somehow, |
39 |
and sed didn't like it. |
40 |
|
41 |
So check your /etc/make.conf. |
42 |
|
43 |
|
44 |
-- |
45 |
Chad Huneycutt try { Windows } |
46 |
Ph.D. Student catch ( Exception BSOD ) |
47 |
Georgia Tech College of Computing { linux }; |
48 |
http://www.cc.gatech.edu/~chadh |