[syslinux] How to make isolinux.bin only?

[Geert Stappers]

On Thu, Sep 06, 2012 at 09:22:31PM +0200, Tomas M wrote:
> On Thu, Sep 6, 2012 at 6:16 PM, Sebastian Herbszt <herbszt at gmx.de> wrote:
> > Tomas M wrote:
> >>
> >> Hello,
> >> I wish to recompile only isolinux.bin and nothing else.

  recompile

> >> I made some changes to core/fs/lib/loadconfig.c and now I wish to make
> >> (compile) isolinux.bin only.
> >>
> >> The only way how to do it seems to be "make" in the directory of
> >> syslinux sources.
> >> But this takes very long and compiles everything.
> >>
> >> Is there a better way to make only isolinux.bin?
> >> Something like "make isolinux" (which obviously doesn't work)
> >
> >
> > make -C core isolinux.bin
> >
> 
> I am afraid this doesn't work.
> When I use 'make -C core isolinux.bin' then I get:
> make: Nothing to be done for isolinux.bin

I can reproduce that expected behaviour:
<screenshot>
stappers at inertia:/usr/src/syslinux
$ LANG=C make -C core isolinux.bin
make: Entering directory `/usr/src/syslinux/core'
make: `isolinux.bin' is up to date.
make: Leaving directory `/usr/src/syslinux/core'
</screenshot>

> (even if I modified some source files which are needed for compilation)

I can't reproduce that reported error:
<screenshot>
stappers at inertia:/usr/src/syslinux
$ touch core/isolinux.asm
stappers at inertia:/usr/src/syslinux
$ LANG=C make -C core isolinux.bin
make: Entering directory `/usr/src/syslinux/core'
nasm -f elf -Ox -g -F dwarf -DDATE_STR="'pre11*'" \
        -DHEXDATE="0x504a29fe" \
        -l isolinux.lsr -o isolinux.o -MP -MD .isolinux.o.d isolinux.asm
ld -m elf_i386  -T syslinux.ld -M -o isolinux.elf isolinux.o \
        --start-group libcore.a ../com32/lib/libcomcore.a /usr/lib/gcc/x86_64-linux-gnu/4.7/32/libgcc.a --end-group \
        > isolinux.map
objdump -h isolinux.elf > isolinux.sec
perl lstadjust.pl isolinux.lsr isolinux.sec isolinux.lst
objcopy -O binary isolinux.elf isolinux.raw
../lzo/prepcore isolinux.raw isolinux.bin
make: Leaving directory `/usr/src/syslinux/core'
stappers at inertia:/usr/src/syslinux
$ 
</screenshot>

> If I remove the pre-existing isolinux.bin file and use 'make -C core
> isolinux.bin', I get:
> make: *** No rule to make target isolinux.bin. Stop.

I can't reproduce that reported error:
<screenshot>
stappers at inertia:/usr/src/syslinux
$ ls -ltr core/isolinux.*
-rw-r--r-- 1 stappers src  30547 sep  7 19:08 core/isolinux.asm
-rw-r--r-- 1 stappers src  69312 sep  7 19:34 core/isolinux.o
-rw-r--r-- 1 stappers src 646971 sep  7 19:34 core/isolinux.lsr
-rw-r--r-- 1 stappers src  67213 sep  7 19:34 core/isolinux.map
-rwxr-xr-x 1 stappers src 193771 sep  7 19:34 core/isolinux.elf
-rw-r--r-- 1 stappers src   3826 sep  7 19:34 core/isolinux.sec
-rwxr-xr-x 1 stappers src  57476 sep  7 19:34 core/isolinux.raw
-rw-r--r-- 1 stappers src 646971 sep  7 19:34 core/isolinux.lst
-rw-r--r-- 1 stappers src  24576 sep  7 19:38 core/isolinux.bin
stappers at inertia:/usr/src/syslinux
$ LANG=C rm core/isolinux.bin 
stappers at inertia:/usr/src/syslinux
$ LANG=C rm core/isolinux.bin 
rm: cannot remove `core/isolinux.bin': No such file or directory
stappers at inertia:/usr/src/syslinux
$ LANG=C make -C core isolinux.bin
make: Entering directory `/usr/src/syslinux/core'
../lzo/prepcore isolinux.raw isolinux.bin
make: Leaving directory `/usr/src/syslinux/core'
stappers at inertia:/usr/src/syslinux
$ ls -ltr core/isolinux.*
-rw-r--r-- 1 stappers src  30547 sep  7 19:08 core/isolinux.asm
-rw-r--r-- 1 stappers src  69312 sep  7 19:34 core/isolinux.o
-rw-r--r-- 1 stappers src 646971 sep  7 19:34 core/isolinux.lsr
-rw-r--r-- 1 stappers src  67213 sep  7 19:34 core/isolinux.map
-rwxr-xr-x 1 stappers src 193771 sep  7 19:34 core/isolinux.elf
-rw-r--r-- 1 stappers src   3826 sep  7 19:34 core/isolinux.sec
-rwxr-xr-x 1 stappers src  57476 sep  7 19:34 core/isolinux.raw
-rw-r--r-- 1 stappers src 646971 sep  7 19:34 core/isolinux.lst
-rw-r--r-- 1 stappers src  24576 sep  7 19:39 core/isolinux.bin
stappers at inertia:/usr/src/syslinux
$ 
</screenshot>



I think that I learned that I shouldn't take a top poster serious.

I could have known that before I did spend on the reported errors,
after all, when a person doesn't understand discussion order,
it will be hard for him to understand high tech stuff.


Groeten
Geert Stappers
-- 
> And is there a policy on top-posting vs. bottom-posting?
Yes.