Just for reference - please do NOT upload any cross compiled packages
if at all possible. It's a little too unreliable.
Dan
>[problems with booting into debian]
you need to upgrade your kernel to a version greater than 2.1.102. try
2.1.115 from ftp.linuxppc.org. this is becoming a faq.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simulta
On 31 Aug 1998, Stefan Berndtsson wrote:
> going for another approach, I chroot from a libc-1.99 system onto the
> base-partition. That works fine at first. However, when trying to install
> anything, I get:
>
> bash-2.01# dpkg -iGE adduser_3.8.deb
> tar: conffiles: Cannot chown to uid 0 gid 0
Hartmut Koptein <[EMAIL PROTECTED]> writes:
My system is an Apple Performa 6400, 180MHz 603e.
Which would've been running debian and glibc-2.1 by now, had I managed
to get the thing working.
If you have any ideas, they would be welcome.
Unpacked base-powerpc.tar.gz
Tried to boot on that partiti
> Using sys-include instead of include is at least unusual...
in binutils, ./configure --target=ppc --with-headers=/other/usr/include
create /usr/local/ppc/sys-include and copies /other/usr/include/* in it.
> Seems so, yes. Do you also have cross-binutils? (You need them.)
i compiled a cross bi
> /usr/local/arch_specific_name/sys-include and not include, like it
> is the default in dpkg-cross.
Using sys-include instead of include is at least unusual... Don't know
if there's a reason for this. You can either make a symlink include ->
sys-include, or change the crossinc variable in
/etc/d
hello, ...
i have played a bit with dpkg-cross and have a remark and a problem with it.
Firstly, when i built my m68k -> ppc cross compiler, it put the includes in :
/usr/local/arch_specific_name/sys-include and not include, like it is the
default in dpkg-cross.
Secondly, i tried to cross bui
> > Wow! Very good, but -sorry- which direction was is?
> > i386 > ppc???
>
> no, m68k -> ppc naturally, with the other side of my apus board, only a '40
> so it is quite slow, but it works . Perhaps i could cross compile you a
> ppc -> m68k corss compiler, would be funny.
>
> err, .. spe
> Wow! Very good, but -sorry- which direction was is?
> i386 > ppc???
no, m68k -> ppc naturally, with the other side of my apus board, only a '40
so it is quite slow, but it works . Perhaps i could cross compile you a
ppc -> m68k corss compiler, would be funny.
err, .. special procedure f
> Hartmut, i have a working cross compiler now, i could cross compile some
> packages ? is this easy to do, is there a special procedure for it ?
Wow! Very good, but -sorry- which direction was is?
i386 > ppc???
i like to have the ppc -> m68k cross compiler.
Special procedure: hmmm d
Hartmut, i have a working cross compiler now, i could cross compile some
packages ? is this easy to do, is there a special procedure for it ?
Friendly,
Sven LUTHER
i will be willing to work on gtk, i will be using it anyway, so why not work on
it.
Friendly,
Sven LUTHER
hello, ...
i have a Amiga 1200 with a 603e Blizzard PowerUP board.
i think you can put :
APUS Blizzard 603e+ (603e/240MHz)
or is it 603p ?
i don't think i will be able to go to oldenburg, but as soon as i have a
working system (we did some big progress this weekend, it don't die anymore in
On Sun, Aug 30, 1998 at 08:36:43PM -0700, Alex Romosan wrote:
> collect2: ld returned 1 exit status
correct me if i'm wrong; shouldn't collect only make an appearance on
machines not using GNU ld? in all my experience i've only encountered this
error on digital unix and solaris boxes using gcc an
the new egcc seems to compile simple c programs, but it doesn't
compile c++. this is what i get when i try to compile this program:
#include
int main(int argc, char** argv)
{
cout << "hello world" << endl;
}
/usr/lib/gcc-lib/powerpc-linux/egcs-2.91.56/libstdc++.so: undefined reference
to `ex
On Sun, Aug 30, 1998 at 07:44:00PM -0700, Alex Romosan wrote:
> >> i have a PowerComputing PowerCenter 132MHz computer on which i run
> >
> >603 or 604 cpu?
>
> it's a 604.
Ok, added!
> >You have a working glibc-2.1 system (now)? Very good!
>
> sort of. i just installed the latest egcc from In
>> i have a PowerComputing PowerCenter 132MHz computer on which i run
>
>603 or 604 cpu?
it's a 604.
>You have a working glibc-2.1 system (now)? Very good!
sort of. i just installed the latest egcc from Incoming, and now i
can't even compile a simple c++ program. i haven't tried c yet. maybe
i'
> >this is a list of people with a powerpc system. It is always good to
> >have such
>
> i have a PowerComputing PowerCenter 132MHz computer on which i run
603 or 604 cpu?
> debian linux (finally managed to boot back, after i deleted the old
> redhat mini-partition). i am also willing to help wi
>this is a list of people with a powerpc system. It is always good to
>have such
i have a PowerComputing PowerCenter 132MHz computer on which i run
debian linux (finally managed to boot back, after i deleted the old
redhat mini-partition). i am also willing to help with the port (i've
been compili
19 matches
Mail list logo
