Re: [microblaze-uclinux] ld segfault

[Chris Robson <Chris.Robson@xxxxxxxxxxxx>]

John

Just ran into another default suggestion or maybe a FAQ.  Well maybe not 
since I'm not sure of the impact. 
Anyway, Within the "Customize Kernel Settings" > "Linux Kernel 
Configuration" > "General Setup" > Initramfs source file> possibly 
having the default string "$(ROOTDIR)/images/rootfs.cpio". 
The fallout from not doing this, in my case, is the target system 
crashes with a kernel panic not being able to mount a file system.

...Chris

John Williams wrote:
> Hi Pablo,
>
> On Thu, May 21, 2009 at 7:32 PM,  <pcolodron@xxxxxxxx> wrote:
>
>   
> > When I compile the application, I can see the following error:
> >
> > microblaze-uclinux/bin/ld: line 168: 27630 Segmentation fault      $LINKER
> > $EMUL -r -d -o "$OFILE.elf2flt" $ARG1
> > collect2: ld returned 139 exit status
> >
> >
> > It is probably a problem related to how I compile the library. Maybe I have
> > some x86 objects in my library and I do not know.
> >     
>
> It is a likely cause.
>
>   
> > Could you tell me Rod or John how to check this? You told that you used the
> > vervose output from mb-strip. Could you explain how to do it?
> >     
>
> Basically take a look at thegcc or ld command line that is triggering
> the bug.  Run that command manually, but att -v (for verbose), it
> should give you a list of all object (.o) and library (.a) files that
> are part of the link.  Ten check each of those with "mb-objdump -t
> <filename>", it shold report them as microblaze binaries.
>
> Regards,
>
> John
>   
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/