public inbox for gentoo-sparc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ferris McCormick <fmccor@gentoo.org>
To: gentoo-sparc@lists.gentoo.org
Subject: [Fwd: Re: [gentoo-sparc] ultra 5/gentoo xorg-x11 questions]
Date: Thu, 08 Dec 2005 19:13:59 +0000	[thread overview]
Message-ID: <1134069239.12900.11.camel@polylepis.inforead.com> (raw)

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

Just a copy of a response to Glenn Burns.  I tried to CC gentoo-sparc in
my response, but misspelled 'sparc'. It's been that sort of day.

-------- Forwarded Message --------
From: Ferris McCormick <fmccor@gentoo.org>
To: glenn <glenn.burns@gmail.com>
Cc: gentoo-soarc@gentoo.org
Subject: Re: [gentoo-sparc] ultra 5/gentoo xorg-x11 questions
Date: Thu, 08 Dec 2005 19:10:58 +0000

On Thu, 2005-12-08 at 11:33 -0600, glenn wrote:
> On 11/22/05, Ferris McCormick <fmccor@gentoo.org> wrote:
> >I do not see how you can compile anything at all
> > on that system at this point.  Just for fun, try something like
> > ebuild /usr/portage/sys-devel/gcc-3.3.5.20050130-r1.ebuild \
> >   fetch unpack compile install
> > (A complete rebuild of the gcc compiler without actually installing it
> > into the running system.)  That build should give your system more
> > exercise that xorg-x11 has for you so far.
> > >
> > --
> > Ferris McCormick (P44626, MI)
> > Developer, Gentoo Linux (sparc, devrel)
> 
> 
> ferris:
> 
> i hope you don't mind me emailing you directly.  i just wanted to let
> you know that i ran the ebuild command above and it was able to
> compile without errors.  i also compiled the kernel at the same time
> to give the box/gcc a workout of sorts. both the kernel compile and
> the ebuild finished with out errors. prior this, i decided to emerge
> -e system and other than a couple of minor issues not related to
> compiles, the emerge -e system also finished without problems.
> 
> i still can't get xorg-x11 to build properly.
> 
> i'm  a complete n00b when it comes to IRC's but i will try to join and
> solicit ideas from there.  i appreciate your help and all the work you
> guys do to make gentoo-sparc happen.
> 
> -=glenn=-
Well, I didn't know anything about IRC until a couple years ago, either,
so it can be done.

I notice that you have had some communication with davem (David Miller).
Be sure to take anything he says very seriously.  He is the lead kernel
person for the sparc linux kernel, and when he suggests concentrating on
your disk, believe him.  As he says, data from the header files is not
making it correctly to the compiler.  If I recall correctly, there are a
lot of symbolic links involved in what leads up to your problem, and
that might be significant.  (I know that in general, when building
xorg-x11, most header files are symbolic links to something else; I just
don't know about your specific failure.)

Regards,
Ferris
-- 
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Sparc, Devrel)

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

                 reply	other threads:[~2005-12-08 19:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1134069239.12900.11.camel@polylepis.inforead.com \
    --to=fmccor@gentoo.org \
    --cc=gentoo-sparc@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