On Sun, Feb 23, 2003 at 01:33:40PM +0100, Matthias Klose wrote:
> > attached. one problem with that: does the compiler needs cpp?
> yes. although the separation doesn't make much sense starting with 3.3
> (integrated cpp).
at least with the current source package the compiler doesn't call the
cpp.
> I would it find easier to put together libgcc1-xxx, cpp-xxx and
> gcc-xxx into one package (gcc-xxx).
the current patch don't install cpp either.
> same for all C++ related packages -> g++-xxx (or put them into
> gcc-xxx) as well. Not sure, if we really need the -pic and -dbg files
> for a cross compiler.
it is possible the use the native libs via dpkg-cross like the glibc.
> the soft-float is dropped for native builds currently. do we need this
> and nof for cross compilers?
i want to use the complete thing for a powerpc without a fpu, so i need
at least the nof.
> good question. never tried to run a testsuite of a cross
> compiler. currently it's run on HOST, so it can run all compile
> tests. dejagnu offers support to run a testsuite on a remote host, but
> I didn't check yet how to do.
i think it should run if "ifndef DEB_CROSS" is evalutated
> > --
> > Captain's Log, star date 21:34.5...
> > --- out.orig 2003-02-23 12:27:43.000000000 +0100
> > +++ out 2003-02-23 12:29:14.000000000 +0100
> > -Depends: ${shlibs:Depends}, binutils-m68k (>= 2.13.90.0.10)
> > +Depends: gcc-3.2-base, libgcc1-m68k (>= 1:3.2.3-0pre1.cross.1), ${shlibs:Depends}, cpp-3.2 (>= 1:3.2.3-0pre1.cross.1), cpp-3.2 (<< 1:3.2.4), ${shlibs:Depends}, binutils-m68k (>= 2.13.90.0.10)
>
> libgcc1-m68k seems to be ok, but why gcc-3.2-base and cpp-3.2?
any native compiler uses gcc-3.2-base, the cross compilers may use that
files also.
i also include cpp-3.2 before i realized that it is never used.
bastian
--
"Get back to your stations!"
"We're beaming down to the planet, sir."
-- Kirk and Mr. Leslie, "This Side of Paradise",
stardate 3417.3
Attachment:
pgpPVpUUjlCUE.pgp
Description: PGP signature