On Tue, 28 Nov 1995, Ian Jackson wrote:
>
> I didn't realise the libc had been hacked so far from the GNU one
> (which has a sophisticated built-time configuration mechanism).
>
> Are the two libcs being maintained (upstream) separately ? If so they
> should probably have different source packa
Matthew Bailey writes ("Re: [EMAIL PROTECTED]: New Linux/SPARC snapshot]
(fwd)"):
> LIBC will cause a major concern here considering the port is HUGE to make
> it all work. The kernel Source tree is not a big deal since it can
> configure most of itself.
I didn't realise the libc had been hacke
Mail Archive writes:
> You know this is where pristine(SP?) sources would be nice that way we
> can apply debian-platform-specific patches to0 the source tree that way
> we only hve to have a so-called-distfiles-directory that is NON platform
> specific. This will make porting MUCH easier...
I
On Mon, 27 Nov 1995, Ian Jackson wrote:
>
> In this day and age there are very few programs that need to have
> different source code to compile on different CPUs.
>
> Lest anyone think that I speak as someone who doesn't have to deal
> with this problem, I'd like to point out that I'm the maint
Date: Sun, 26 Nov 1995 21:04:26 -0500 (EST)
From: Mail Archive <[EMAIL PROTECTED]>
Bruce: Can we get a list called debian-sparc for the active work on the
sparc port?
Ian M.: Can we start setting up a tree? Make sure it says under
contruction or somesuch
David Miller: Do
Bruce: Can we get a list called debian-sparc for the active work on the
sparc port?
Ian M.: Can we start setting up a tree? Make sure it says under
contruction or somesuch
David Miller: Do you want to be added to this list I assume it will be a
moderate traffic list...
I will try to get
6 matches
Mail list logo
