On Sat, Apr 10, 2010 at 5:54 PM, Bahadir Balban <baha...@l4dev.org> wrote:
> Drasko DRASKOVIC wrote: > > On Sat, Apr 10, 2010 at 4:57 PM, Lin Yu <yulin...@gmail.com> wrote: > > > >> Hi, guys, > >> > >> I had same problem. > >> > >> But after I changed to scons 1.2, everything is ok. > >> > > > > Might be that I have some mutant version of scons as I tried installing > 1.3 > > over 1.2 . > > > > I will try to remove it and install again 1.2. > > > > BR, > > Drasko > > > > It might not be a versioning problem. I suspect that it happens due to > images.S being generated in the source tree rather than under the build > directory. > I confirm that it was a scons versioning problem. It works fine with scons 1.2. > > Can you try removing loader/images.S if it exists. It does not exist as it has never been generated. When I force ignoring errors in scons it is generated, and next time scons does not complain, as images.S is present (as I noted before, itmight dependecies problem in scons script). > Then do: > > scons -f SConstruct.loader > It breaks as I described before. > > What do you get? I get: > > baha...@bahadir-laptop:~/codezero-v3$ scons -f SConstruct.loader > scons: Reading SConscript files ... > scons: done reading SConscript files. > scons: Building targets ... > gen_loader_images_S(["loader/images.S"], ["build/kernel.elf", > "build/conts/containers.elf"]) > Nope, here it breaks with scons 1.3 telling that images.S is not present. BR, Drasko
_______________________________________________ codezero-devel mailing list codezero-devel@lists.l4dev.org http://lists.l4dev.org/mailman/listinfo/codezero-devel
