public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-core@gentoo.org, Gentoo-Dev <gentoo-dev@gentoo.org>,
	Gentoo-User <gentoo-user@gentoo.org>
Subject: [gentoo-dev] Possible isses with gcc, *please* read!
Date: 17 Dec 2002 00:21:15 +0200	[thread overview]
Message-ID: <1040077275.15406.31.camel@nosferatu.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

Hi

Sorry for the inconvenience, but if you experience problems
where builds fail due to /lib/cpp or /usr/bin/cc not being
executable:

-----------------------
imake -DUseInstalled -I/usr/X11R6/lib/X11/config 
imake: No such file or directory 
imake: Cannot exec /lib/cpp. 
  Stop. 
-----------------------

Please do the following:

 # emerge rsync
 # rm -f /lib/cpp /usr/bin/cc
 # cp /usr/portage/sys-devel/gcc/files/cpp /lib
 # cp /usr/portage/sys-devel/gcc/files/cc /usr/bin
 # chmod +x /lib/cpp /usr/bin/cc

The reason for this, is that for support of multiple versions
of gcc, we had to drop the /lib/cpp and /usr/bin/cc symlinks
in favour for wrappers.

Problem now, is that many of the older gcc ebuild have a broken
pkg_postrm() function that recreate the /lib/cpp and /usr/bin/cc
symlinks after new one was merged, and old is then unmerged.

If any problems, and above does not work, drop me a mail ... I
will try to help everyone in reasonable time.


Regards,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2002-12-16 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 22:21 Martin Schlemmer [this message]
2002-12-17 10:10 ` [gentoo-dev] Re: Possible isses with gcc, *please* read! Csaba Paradi

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=1040077275.15406.31.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-core@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-user@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