Gentoo Archives: gentoo-user

From: Joseph <syscon780@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] [SOLVED] can not compile / emerge
Date: Wed, 10 Sep 2014 05:20:51
Message-Id: 20140910052044.GA20894@syscon7
In Reply to: Re: [gentoo-user] [SOLVED] can not compile / emerge by Kerin Millar
1 On 09/10/14 06:01, Kerin Millar wrote:
2 >On 10/09/2014 05:16, Joseph wrote:
3 >> On 09/10/14 04:57, Kerin Millar wrote:
4 >>> On 10/09/2014 04:50, Joseph wrote:
5 >>>> On 09/10/14 04:27, Kerin Millar wrote:
6 >>>>> On 10/09/2014 04:21, Joseph wrote:
7 >>>>>> On 09/10/14 03:59, Kerin Millar wrote:
8 >>>>>>> On 09/09/2014 19:36, Joseph wrote:
9 >>>>>> [snip]
10 >>>>>>
11 >>>>>>>>
12 >>>>>>>> Running on my other system I get:
13 >>>>>>>> equery b libstdc++.so.6
14 >>>>>>>> * Searching for libstdc++.so.6 ... sys-devel/gcc-4.5.4
15 >>>>>>>> (/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 ->
16 >>>>>>>> libstdc++.so.6.0.14)
17 >>>>>>>>
18 >>>>>>>> env-update - doesn't work either
19 >>>>>>>>
20 >>>>>>>
21 >>>>>>> Check beneath /etc/env.d/ld.so.conf.d and ensure that there is a file
22 >>>>>>> defining the appropriate paths for your current version of gcc.
23 >>>>>>> Here's
24 >>>>>>> how it looks on my system:
25 >>>>>>>
26 >>>>>>> # cd /etc/ld.so.conf.d
27 >>>>>>> # ls
28 >>>>>>> 05binutils.conf 05gcc-x86_64-pc-linux-gnu.conf
29 >>>>>>> # cat 05gcc-x86_64-pc-linux-gnu.conf
30 >>>>>>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32
31 >>>>>>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3
32 >>>>>>>
33 >>>>>>> Once you have made any necessary changes, run ldconfig.
34 >>>>>>>
35 >>>>>>> --Kerin
36 >>>>>>
37 >>>>>> Thanks Kerin, for the pointer.
38 >>>>>> I think I have a bigger problem, and don't know how to fix it.
39 >>>>>>
40 >>>>>> Yes, I have the same file /etc/ld.so.conf.d
41 >>>>>> # ls # 05gcc-x86_64-pc-linux-gnu.conf
42 >>>>>> # cat /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32
43 >>>>>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3
44 >>>>>>
45 >>>>>> However, those directories are empty (only one file):
46 >>>>>> # ls -al /usr/lib/
47 >>>>>> libbrcomplpr2.so
48 >>>>>
49 >>>>> Is /usr/lib an actual directory or a symlink? Assuming that you use a
50 >>>>> stock amd64 (multilib) profile, it should be a symlink to lib64. If you
51 >>>>> find that it is a directory and that you also have a lib64 directory,
52 >>>>> try the commands below. You can skip the busybox and exit commands if
53 >>>>> you are doing this in a chroot rather than on a live system.
54 >>>>>
55 >>>>> # busybox sh
56 >>>>> # cd /usr/
57 >>>>> # mv lib lib.old
58 >>>>> # ln -s lib64 lib
59 >>>>> # exit
60 >>>>>
61 >>>>>> On my other working system this directory "/usr/lib/" contain about
62 >>>>>> 2020
63 >>>>>> files.
64 >>>>>> What had happened?
65 >>>>>> After emerging some files and system I was running command: fstrim
66 >>>>>> -v /
67 >>>>>> (as the disk is SSD).
68 >>>>>> Could it have something to do with the fact that these directories are
69 >>>>>> empty?
70 >>>>>
71 >>>>> No. Using fstrim does not delete files.
72 >>>>>
73 >>>>> --Kerin
74 >>>>
75 >>>> Kerin you are a magician! THANK YOU!!!
76 >>>> Yes, it worked. Everything is back to normal.
77 >>>>
78 >>>> I can still not comprehend what had happened :-/ why all of a sudden in
79 >>>> the middle of compilation it all vanished.
80 >>>
81 >>> Were you doing anything outside of portage that may have had a hand in
82 >>> it?
83 >>>
84 >>> Incidentally, you should move libbrcomplpr2.so to /usr/lib32. Some
85 >>> googling suggests to me that it is a library included in a proprietary
86 >>> Brother printer driver package. You can use the file command to confirm
87 >>> that it is a 32-bit library.
88 >>>
89 >>> --Kerin
90 >>
91 >> I was logged in over ssh in one terminal, compiling "xsane"
92 >> and logged in, in another terminal and was installing brother printer
93 >> driver (without emerge) manual installation.
94 >> I followed my own instructions from:
95 >> http://forums.gentoo.org/viewtopic-t-909052-highlight-brother.html?sid=1ba0b92db499262c6a74919d86c6af43
96 >>
97 >>
98 >> I run: tar zxvf ./hl5370dwlpr-2.0.3-1.i386.tar.gz -C / tar zxvf
99 >> ./cupswrapperHL5370DW-2.0.4-1.i386.tar.gz -C /
100 >> Could be that one of this script messed up the links.
101 >> If so I don't know how could it happen. Looking though "history" these
102 >> are the commands I run:
103 >>
104 >> 305 tar zxvf ./brhl5250dnlpr-2.0.1-1.i386.tar.gz -C /
105 >> 306 tar zxvf ./cupswrapperHL5250DN-2.0.1-1.i386.tar.gz -C /
106 >> 307 cd /usr/local/Brother/cupswrapper
107 >> 308 mv cupswrapperHL5250DN-2.0.1 cupswrapperHL5250DN-2.0.1.bak
108 >> 309 /bin/sed 's/\/etc\/init.d\/cups\ restart/\/etc\/init.d\/cupsd\
109 >> restart/g' ./cupswrapperHL5250DN-2.0.1.bak > ./cupswrapperHL5250DN-2.0.1
110 >> 310 ls -al
111 >> 311 pwd
112 >> 312 ll
113 >> 313 ls -al
114 >> 314 chmod 755 cupswrapperHL5250DN-2.0.1
115 >>
116 >> I just extracted the files with "tar..."
117 >
118 >I read your forum post and can see that you're (dangerously) extracting
119 >directly into the root directory and that this is among the contents of
120 >the archive:
121 >
122 > ./usr/lib/
123 > ./usr/lib/libbrcomplpr2.so
124 >
125 >I posit that tar clobbers the /usr/lib symlink, converting it into a
126 >directory because that is what is stored in the archive.
127 >
128 >Ergo, use the --keep-directory-symlink parameter.
129 >
130 >--Kerin
131
132 Thank you again, I've already modified the line (so hopefully nobody else will get caught in it):
133 eg. tar --keep-directory-symlink -zxvf ./hl5370dwlpr-2.0.3-1.i386.tar.gz -C /
134
135 --
136 Joseph