On Thu, 2005-05-05 at 23:20 +0200, Sam Ravnborg wrote:
> > > In any case, there's no reason to mess with that at all. This stuff is
> > > trivally dealt with by a wrapper script that takes target name as its
> > > first argument (the rest is passed to make unchanged) and figures out
> > > ARCH, CROSS_COMPILE, SUBARCH and build directory by it. End of story.
> >
> > I'm using such script now. It's called kmake.
>
> Use a Makefile called either makefile or GNUMakefile to call make with
> correct arguments. No kmake script required.
> And no difference in behaviour using O= or not.
> You could teach kmake to create such a file if not present.
Or we could teach scripts/mkmakefile to do it for all of us. I can post
a patch that would call scripts/mkmakefile regardless of whether O= is
used, and scripts/mkmakefile would generate makefile rather than
Makefile.
> > I keep forgetting to run
> > kmake instead of make, so it's an annoyance for me (usually it end up
> > with a full screen of error messages, but I'm afraid I could get a mix
> > of object files for different architectures in some cases).
>
> Nope. .o files are rebuild if commandline changes. This works well.
> This works so well that when you change name of gcc you have to rebuild
> the kernel - no matter the arguments used.
> It amy be a shift from gcc 2.96 to gcc 4.0.
Good to know. But my point still stands.
If I have a build tree already compiled for a specific architecture, and
I'm going to compile an external driver against that tree, why do I need
to set ARCH and CROSS_COMPILE to match those used during compilation?
Why cannot the build system do it for me?
Also, if I want to recompile the kernel after changing the source, I
want to run make in the build tree. That's what the generated Makefile
is for. But if I overrode ARCH or CROSS_COMPILE, I have to remember to
do it again. And that's what I want to fix.
I'm sure I can write a very intelligent script tuned for my system that
would do the right thing and that will even set CROSS_COMPILE based on
the architecture from .config file. But I want to share my code, not to
hoard it.
Maybe I should try to implement saving ARCH and CROSS_COMPILE in .config
file, but it would be more intrusive.
--
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
