public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joseph <syscon780@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can not compile / emerge
Date: Tue, 9 Sep 2014 21:21:23 -0600	[thread overview]
Message-ID: <20140910032123.GA12488@syscon7> (raw)
In-Reply-To: <540FBEAA.2050906@fastmail.co.uk>

On 09/10/14 03:59, Kerin Millar wrote:
>On 09/09/2014 19:36, Joseph wrote:
[snip]

>>
>> Running on my other system I get:
>> equery b libstdc++.so.6
>> * Searching for libstdc++.so.6 ... sys-devel/gcc-4.5.4
>> (/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 ->
>> libstdc++.so.6.0.14)
>>
>> env-update - doesn't work either
>>
>
>Check beneath /etc/env.d/ld.so.conf.d and ensure that there is a file
>defining the appropriate paths for your current version of gcc. Here's
>how it looks on my system:
>
>   # cd /etc/ld.so.conf.d
>   # ls
>   05binutils.conf  05gcc-x86_64-pc-linux-gnu.conf
>   # cat 05gcc-x86_64-pc-linux-gnu.conf
>   /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32
>   /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3
>
>Once you have made any necessary changes, run ldconfig.
>
>--Kerin

Thanks Kerin, for the pointer.
I think I have a bigger problem, and don't know how to fix it.

Yes, I have the same file /etc/ld.so.conf.d
# ls 
# 05gcc-x86_64-pc-linux-gnu.conf
# cat 
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3

However, those directories are empty (only one file):
# ls -al /usr/lib/
libbrcomplpr2.so

On my other working system this directory "/usr/lib/" contain about 2020 files.
What had happened?  

After emerging some files and system I was running command: fstrim -v / (as the disk is SSD).
Could it have something to do with the fact that these directories are empty?
-- 
Joseph


  reply	other threads:[~2014-09-10  3:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 18:36 [gentoo-user] can not compile / emerge Joseph
2014-09-09 18:45 ` Joseph
2014-09-09 18:46 ` Todd Goodman
2014-09-09 19:02   ` Joseph
2014-09-09 19:15   ` Joseph
2014-09-09 21:38     ` Mick
2014-09-09 21:57       ` Joseph
2014-09-09 22:20         ` Neil Bothwick
2014-09-09 22:49           ` Joseph
2014-09-10  3:29       ` Kerin Millar
2014-09-09 18:49 ` Dale
2014-09-10  2:59 ` Kerin Millar
2014-09-10  3:21   ` Joseph [this message]
2014-09-10  3:27     ` Kerin Millar
2014-09-10  3:50       ` [gentoo-user] [SOLVED] " Joseph
2014-09-10  3:57         ` Kerin Millar
2014-09-10  4:16           ` Joseph
2014-09-10  5:01             ` Kerin Millar
2014-09-10  5:10               ` Kerin Millar
2014-09-10  5:32                 ` [gentoo-user] BACKUPS Joseph
2014-09-10  7:14                   ` Alan McKinnon
2014-09-10  7:47                     ` Dale
2014-09-10  7:51                       ` J. Roeleveld
2014-09-10  8:03                         ` Dale
2014-09-10  9:13                           ` Alan McKinnon
2014-09-10  8:34                     ` Neil Bothwick
2014-09-10 11:03                   ` Kerin Millar
2014-09-10  5:20               ` [gentoo-user] [SOLVED] can not compile / emerge Joseph
2014-09-11 12:07             ` [gentoo-user] " James
2014-09-11 12:28               ` Joseph
2014-09-11 13:36                 ` J. Roeleveld
2014-09-12 17:09                   ` Joseph
2014-09-11 13:40                 ` James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140910032123.GA12488@syscon7 \
    --to=syscon780@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox