Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: Matthew Wilcox <willy@debian.org>,
	parisc-linux@lists.parisc-linux.org, baldric-exec@baldric.uwo.ca
Subject: Re: [parisc-linux] Building from scratch.
Date: Tue, 28 Aug 2001 16:36:39 -0400	[thread overview]
Message-ID: <20010828163639.C4741@megatonmonkey.net> (raw)
In-Reply-To: <20010828204458.B2995@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Tue, Aug 28, 2001 at 08:44:58PM +0100

> 
> Yes, but you were crosscompiling.  `make install' is very different
> with a crossbuild.
> 

What are the major differences? Crosscompiling vs. Crossbuild?
Better yet, where can I learn about those difference?

> 
> THe program which is being run is
> /home/willy/glibc/2.2.4-1/glibc-2.2.4/hppa-linux/obj/timezone/zic; glibc
> is making sure it's run with the new ld.so and all the new versions of
> the libs.
> 

So the native build of zic barfs. I'm not even sure if zic runs when
you compile glibc by hand? Hrm... zic.c is 52,000 loc.. eww.


> Have you actually tried installing glibc 2.2.4-1 on a live system and
> running programs with it?
> 
> It's more likely that one of the other debian patches conflicts with
> what we're doing.  The debian/rules file will apply the patches in the
> debian/patches directory in the order given by debian/patches/0list.
> I seem to remember a couple of other diffs that need to get applied...

Question:
In theory since those patches are changes that haven't been merged upstream,
should the only requirements be:

- Have 2.2.4 Original
- Carry out any one of the dpatch's since they are dif'd against 2.2.4 Original
- Then carry out the 2.2.4-1 patch

For x86 Cross Compiler, the only requirement would be:
- Apply the dpatch's that are critical to the running hppa port

Quesiton:
If the pool has the hppa changes commented out in the 0list file, does
that mean that glibc2.2.4 is not available for hppa yet? (Since it fails to 
compile? The first error probably being the Elf32_Addr* problem with
that '& 3' fixed by a cast to (unsigned int)).

> 
> That's changing all the testandset to trylock.
>

Why would that be in the hppa dpatch?

Cheers,
Carlos. 

  reply	other threads:[~2001-08-28 20:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-26 20:27 [parisc-linux] Building from scratch Carlos O'Donell Jr.
2001-08-27 19:38 ` Matthew Wilcox
2001-08-28  3:54   ` Carlos O'Donell Jr.
2001-08-28  4:39   ` Carlos O'Donell Jr.
2001-08-28  5:10     ` Matthew Wilcox
2001-08-28 11:17       ` Carlos O'Donell Jr.
2001-08-28 14:56         ` Matthew Wilcox
2001-08-28 15:29           ` Carlos O'Donell Jr.
2001-08-28 18:47             ` Matthew Wilcox
2001-08-28 19:22               ` Carlos O'Donell Jr.
2001-08-28 19:44                 ` Matthew Wilcox
2001-08-28 20:36                   ` Carlos O'Donell Jr. [this message]
2001-08-28 20:47                     ` Matthew Wilcox
2001-08-28 15:06         ` Carlos O'Donell Jr.

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=20010828163639.C4741@megatonmonkey.net \
    --to=carlos@megatonmonkey.net \
    --cc=baldric-exec@baldric.uwo.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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