Re: ld.script

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Putting the LONG(0) right after *(initcall.init) made
the problem go away. So,it is gotta be in the section
description.

Thanks.

--- Håvard_Skinnemoen <skinnemo@itk.ntnu.no> wrote:
> On Thursday, Jul 31, 2003, at 21:42 Europe/Oslo,
> PoIsOn wrote:
> 
> > Hi all,
> >
> > I need to add a few bytes of 0's in my vmlinux
> object
> > file.So I have added a LONG(0) statement in
> > arch/mips/ld.script. But the linker spits out a
> parse
> > error at that line when I do a 'make'
> >
> > Here is the snippet:
> > . = ALIGN(32);   	
> >   __initcall_start = .;
> >   .initcall.init : { *(.initcall.init) }
> >   __initcall_end = .;
> >   LONG(0)
> >   . = ALIGN(4096);	/* Align double page for
> > init_task_union */
> >   __init_end = .;
> >
> > Can somebody say what is wrong in here?
> 
> I would guess that you need a semicolon after
> LONG(0). Or, I think 
> maybe LONG() is only valid inside a section
> description. Try to put it 
> just after *(.initcall.init).
> 
> Håvard
> 
> --
> Kernelnewbies: Help each other learn about the Linux
> kernel.
> Archive:      
> http://mail.nl.linux.org/kernelnewbies/
> FAQ:           http://kernelnewbies.org/faq/
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux