All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nelson Abramson <pogtal@erols.com>
To: Rob Cascella <rob@schizophrenia.dfjp.com>
Cc: john peter grimes <jpgrimes@rainbow.uchicago.edu>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: KDE 2.0 compilation problems
Date: Wed, 03 May 2000 22:49:11 -0400	[thread overview]
Message-ID: <3910E527.75AEF846@erols.com> (raw)
In-Reply-To: 200005040057.UAA02407@schizophrenia.dfjp.com


Rob Cascella wrote:

> I don't know if it's related or not, but I've been trying to compile
> something with g++ and have been getting an error message saying that
> the compiler couldn't create executables.  I tried recompiling gcc,
> but it didn't seem to help.  And, now that I think about it, I'd like
> to try to resolve this issue, so, can anyone help me with this?  I'd
> appreciate it..

This has come up quite a few times on the user list.  You need to have the full
range of gcc related files; binutils, glibc, libstdc, cpp, etc.  Search the
archives for the complete list.

HTH
--Nelson Abramson

--
"Apparently if you play the Windows NT CD backwards you hear satanic messages"
"You think that's bad, if you play it forwards it installs Windows NT!"
--orlando


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-05-04  2:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-28  0:42 XFree 4.0 dual monitor on AGP G4 W. Taylor Holliday
2000-04-28  6:06 ` Michel Dänzer
2000-05-04  0:24 ` KDE 2.0 compilation problems john peter grimes
2000-05-04  0:57   ` Rob Cascella
2000-05-04  2:49     ` Nelson Abramson [this message]
2000-05-04  7:06   ` Kostas Gewrgiou
2000-05-04 15:39     ` john peter grimes
     [not found] ` <Pine.SGI.3.96.1000503191045.17758D-100000@rainbow.uchicago .edu>
2000-05-04 10:33   ` Franz Sirl

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=3910E527.75AEF846@erols.com \
    --to=pogtal@erols.com \
    --cc=jpgrimes@rainbow.uchicago.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=rob@schizophrenia.dfjp.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.