Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] what i did on my holidays
Date: Thu, 27 Sep 2001 20:44:51 -0400	[thread overview]
Message-ID: <20010927204451.F2611@megatonmonkey.net> (raw)
In-Reply-To: <20010927161004.E16096@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Thu, Sep 27, 2001 at 04:10:04PM +0100

> 
> And much much more!
> 
> I haven't even tried compiling it since fixing up the cvs merge conflicts
> with all the good work done in the last week or so.  Have fun...
> 
> -- 

You da best! :)

I've been hacking glibc 2.2.4-1:

	- ./sysdeps/ia64/dl-fptr.c changes for try_lock
	- Put change back into dpatch
	
	- Combing through glibc trying to understand the various
	  changes that have been made (and how glibc works).

	- dpkg-buildpackage now makes it to the point of using a new
	  ld.so.1, which seg's... so I'm back to figuring out why.

I'm still not as far as you've gotten. I can't even get within arms
reach of running zic, though I'm getting closer.

Trying to document those g++ problems with #define _BSD_SOURCE that
Zimmerman has been trying to assign blame for ;)

I constantly mull over writing a new "building the toolchain" for
the website.

Then I listen to Tom Waits, and I just feel like drinking and pondering
if my 715/50 really loves me ;)

--


c.

  reply	other threads:[~2001-09-28  0:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 15:10 [parisc-linux] what i did on my holidays Matthew Wilcox
2001-09-28  0:44 ` Carlos O'Donell Jr. [this message]
2001-09-28 14:23   ` Matthew Wilcox
2001-09-28 17:37     ` Carlos O'Donell Jr.
2001-09-28 20:11       ` Matt Taggart

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=20010927204451.F2611@megatonmonkey.net \
    --to=carlos@megatonmonkey.net \
    --cc=parisc-linux@parisc-linux.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