All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Taggart <taggart@carmen.fc.hp.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: "Paul J.Y. Lahaie" <pjlahaie@linuxcare.com>,
	parisc-linux@puffin.external.hp.com
Subject: Re: [parisc-linux] Weird compile problems
Date: Tue, 30 Jan 2001 16:36:03 -0700	[thread overview]
Message-ID: <20010130233603.B823337C90@carmen.fc.hp.com> (raw)
In-Reply-To: Message from Alan Modra <alan@linuxcare.com.au> of "Wed, 31 Jan 2001 10:25:21 EST." <Pine.LNX.4.21.0101310956430.19209-100000@front.linuxcare.com.au>


Alan Modra writes...

> On Tue, 30 Jan 2001, Paul J.Y. Lahaie wrote:
> 
> [about pehc CVS devel branch gcc]
> > And fixincl (the progrma that does the subst) is taking 0% CPU (from top)
> > 10727 pjlahaie   9   0   712  712   520 S      20  0.0  0.5   0:00 fixincl
> 
> Yeah, fixincl dies for me too.  I'd been putting it down to some sort of
> kernel problem, and just disabled fixinc (gcc/Makefile:STMP_FIXINC).
> Other than that, I get a successful bootstrap, and both kernel & glibc
> compile natively - except that `make' died randomly in the glibc build,
> and I currently have a ld.so.1 that segfaults.

I suspect that your make actually died during the make install right? This is 
the problem that John Marvin and I are working on. The pthread changes that he 
made broke things that use librt and libpthread. In our current nfsroot that 
is tar, make, and sleep. For now we're using a static make to complete the 
install. Once I have a new glibc package built I will do new new 
make,tar,sleep stuff too.

> Hmm, looking at what I just wrote, you can hardly call it a "successful
> bootstrap".  I'm investigating the ld.so.1 problem - at least that one is
> reproducable.

I was seeing that here too but John wasn't. We're currently trying to 
determine the differences in our build environments. What system are you 
building on and what nfsroot/kernel are you using?

Thanks,

-- 
Matt Taggart        Linux Development Lab
taggart@fc.hp.com   HP Linux Systems Operation

  reply	other threads:[~2001-01-30 23:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010130154256.D6704@achilles.net>
2001-01-30 23:25 ` [parisc-linux] Weird compile problems Alan Modra
2001-01-30 23:36   ` Matt Taggart [this message]
2001-01-30 23:45     ` Alan Modra
2001-01-31  1:01   ` Alan Modra
2001-01-31  7:07     ` Alan Modra
2001-02-01  3:59       ` Alan Modra
2001-01-24 21:28 Paul J.Y. Lahaie
2001-01-25  5:58 ` Randolph Chung

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=20010130233603.B823337C90@carmen.fc.hp.com \
    --to=taggart@carmen.fc.hp.com \
    --cc=alan@linuxcare.com.au \
    --cc=parisc-linux@puffin.external.hp.com \
    --cc=pjlahaie@linuxcare.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.