[parisc-linux] crt1.o

[parisc-linux] crt1.o

[Josiah Carlson]

To summarize my current installation:
.5 image copied onto hard drive
base.tgz installed
nfsroot from 10-05-2000
ftp.deb (works great BTW)

>From here I've tried to configure MPICH for compilation...though I keep
getting a crt1.o not found error, even though it exists in /usr/lib.
I tried re-extracting the glibc tarball in /install/debian-hppa, but I
keep getting the same error.
Remembering the problems with caching I tried sync, but that didn't
work.

Just to try something out...I 'm curious as to which file contains the
listing of paths that are searched for libraries by gcc or g++ (or in
general all paths searched by the shell for execution), does anyone know
which file that is?
Or has anyone else had this problem, even after getting crt1.o into
/usr/lib?
Thank you,
 - Josiah

Re: [parisc-linux] crt1.o

[John David Anglin]

> Just to try something out...I 'm curious as to which file contains the
> listing of paths that are searched for libraries by gcc or g++ (or in
> general all paths searched by the shell for execution), does anyone know
> which file that is?

Try running gcc with `-print-search-dirs'.  You can get complete list of gcc
options with `-v --help'.  `-v' may help to see how linker is being run.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

Re: [parisc-linux] crt1.o

[Richard Hirst]

On Tue, Jan 23, 2001 at 04:37:40PM -0600, Josiah Carlson wrote:
> To summarize my current installation:
> .5 image copied onto hard drive
> base.tgz installed
> nfsroot from 10-05-2000
> ftp.deb (works great BTW)
> 
> >From here I've tried to configure MPICH for compilation...though I keep
> getting a crt1.o not found error, even though it exists in /usr/lib.

The quote below is from last October - don't know if it will help
you.

Richard


> > 10:~# make mlock 
> > cc     mlock.c   -o mlock
> > /usr/bin/ld: cannot open crt1.o: No such file or directory
> > collect2: ld returned 1 exit status
> > make: *** [mlock] Error 1
> > 
> > 
> 
> According to Bdale, the fix is:
> 
> ln -s /usr/lib /usr/hppa-linux/lib
> 
> randolph

Re: [parisc-linux] crt1.o

[Josiah Carlson]

> > Just to try something out...I 'm curious as to which file contains the
> > listing of paths that are searched for libraries by gcc or g++ (or in
> > general all paths searched by the shell for execution), does anyone know
> > which file that is?
> 
> Try running gcc with `-print-search-dirs'.  You can get complete list of gcc
> options with `-v --help'.  `-v' may help to see how linker is being run.

I suppose I should have said so...but the actual command being used to
find the libraries is ld.  I've tried to figure that command out...but
it's not liking me at all.
I have not tried the -print-search-dirs on my HP machine, but will
tomorrow.
Though in general, how do I add paths to be searched by the OS?
Thank you,
 - Josiah

Re: [parisc-linux] crt1.o

[John David Anglin]

> > > Just to try something out...I 'm curious as to which file contains the
> > > listing of paths that are searched for libraries by gcc or g++ (or in
> > > general all paths searched by the shell for execution), does anyone know
> > > which file that is?
> > 
> > Try running gcc with `-print-search-dirs'.  You can get complete list of gcc
> > options with `-v --help'.  `-v' may help to see how linker is being run.
> 
> I suppose I should have said so...but the actual command being used to
> find the libraries is ld.  I've tried to figure that command out...but
> it's not liking me at all.
> I have not tried the -print-search-dirs on my HP machine, but will
> tomorrow.
> Though in general, how do I add paths to be searched by the OS?
> Thank you,

Gcc has builtin defaults.  You shouldn't need to specify a search patch
for crt0.o.  Including `-v' on the gcc command will show the stuff that
is being passed to ld.

-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

[parisc-linux] Step by step .... 9000/720 and interruption (trap) 18

[Christoph Plattner]

Hallo PA RISC hackers !

I mentioned before, that I have problems using my Apollo 700 (9000/720)
with the Linux here. I build a new cross tool chain and a new
kernel + palo (all from 13.Jan 2001) but I always have the problem of
looping error code:

handler_interruption() pid=1 command='init'

or whatever my first process is. I have instrumented the kernel code
and added the output of the code number (a good idea to have this
fix in the kernel !) and I saw:

	code=18

So I have the code 18 (decimal). In the PA RISC 1.1 manual (your link)
I saw following description:

	18  Data memory protection trap / Unaligned data reference trap

So what does this mean here. An alignment problem ?
Why is this code not handled in the switch/case ?

I always use (I think the 32bit code). Have I set to a parisc64 ?
How can I influence this ?
Which kind of CPU is this in the 720 model ? (I know a 50MHz PA RISC ..)

I hope anybody can help here

	Christoph




-------------------------------------------------------------------------
private:	christoph.plattner@dot.at
company:	christoph.plattner@alcatel.at