04 Aug, 2010

1 commit


03 Aug, 2010

2 commits

  • It is now possible to assign options to AS and CC
    on the command line - which is only used for built-in code.

    {A,C}FLAGS_KERNEL was used both in the top-level Makefile
    in the arch makefiles, thus users had no way to specify
    additional options to AS, CC without overriding
    the original value.

    Introduce a new set of variables KBUILD_{A,C}FLAGS_KERNEL
    that is used by arch specific files and free up
    {A,C}FLAGS_KERNEL so they can be assigned on
    the command line.

    All arch Makefiles that used the old variables has been updated.

    Signed-off-by: Sam Ravnborg
    Cc: Tony Luck
    Cc: Hirokazu Takata
    Signed-off-by: Michal Marek

    Sam Ravnborg
     
  • It is now possible to assign options to AS, CC and LD
    on the command line - which is only used when building modules.

    {A,C,LD}FLAGS_MODULE was all used both in the top-level Makefile
    in the arch makefiles, thus users had no way to specify
    additional options to AS, CC, LD when building modules
    without overriding the original value.

    Introduce a new set of variables KBUILD_{A,C,LD}FLAGS_MODULE
    that is used by arch specific files and free up
    {A,C,LD}FLAGS_MODULE so they can be assigned on
    the command line.

    All arch Makefiles that used the old variables has been updated.

    Note: Previously we had a MODFLAGS variable for both
    AS and CC. But in favour of consistency this was dropped.
    So in some cases arch Makefile has one assignmnet replaced by
    two assignmnets.

    Note2: MODFLAGS was not documented and is dropped
    without any notice. I do not expect much/any breakage
    from this.

    Signed-off-by: Sam Ravnborg
    Cc: Denys Vlasenko
    Cc: Haavard Skinnemoen
    Cc: Mike Frysinger
    Cc: Tony Luck
    Cc: Geert Uytterhoeven
    Cc: Ralf Baechle
    Cc: Benjamin Herrenschmidt
    Cc: Martin Schwidefsky
    Cc: Chen Liqin
    Acked-by: Mike Frysinger [blackfin]
    Acked-by: Haavard Skinnemoen [avr32]
    Signed-off-by: Michal Marek

    Sam Ravnborg
     

09 Feb, 2010

1 commit

  • This has been broken since May 2008 when Al Viro killed altroot support.
    Since nobody has complained, it would appear that there are no users of
    this code (A plausible theory since the main OSVs that support ia64 prefer
    to use the IA32-EL software emulation).

    Signed-off-by: Tony Luck

    Tony Luck
     

12 Dec, 2009

1 commit


12 Aug, 2009

1 commit

  • Between GCC version 3.4.0 and 4.3.3 (including 3.4.0 and 4.3.3), -mtune=merced
    is implemented in GCC. Starting from 4.4.0, -mtune=merced is deprecated.

    Even implemented in versions between 3.4.0 and 4.3.3, the -mtune=merced
    feature has been broken in some of the versions. For example, GCC 4.1.2 reports
    interanl tuning function errors during kernel building with -mtune=merced. Or
    GCC Bugzilla 16130 reports another -mtune=merced issue on GCC 3.4.1.

    So I would remove the -mtune=merced from IA64 kernel build. Without this option,
    kernel on Merced will remain the same except losing an unstable and out-of-date
    performance tunning feature.

    Since GCC version 3.4.0, -mtune=mckinley has been implemented. The
    -mtune=mckinley option functions the same as mtune=itanium2. And mtune=itanium2
    is the default option. So we don't need to add mtune=mckinley either since its
    been the default option in any GCC version which implements this option.

    Signed-off-by: Fenghua Yu

    Fenghua Yu
     

18 Oct, 2008

3 commits


18 Jul, 2008

1 commit


17 Jun, 2008

1 commit


28 May, 2008

1 commit

  • Make NR_IRQ overridable by each pv instances.
    Pv instance may need each own number of irqs so that
    NR_IRQS should be the maximum number of nr_irqs each
    pv instances need.

    Cc: Jes Sorensen
    Signed-off-by: Isaku Yamahata
    Signed-off-by: Tony Luck

    Isaku Yamahata
     

15 May, 2008

1 commit


27 Apr, 2008

1 commit


05 Mar, 2008

1 commit


08 Dec, 2007

1 commit


16 Oct, 2007

1 commit

  • The variable CPPFLAGS is a wellknown variable and the usage by
    kbuild may result in unexpected behaviour.

    This patch replace use of CPPFLAGS with KBUILD_CPPFLAGS all over the
    tree and enabling one to use:
    make CPPFLAGS=...
    to specify additional CPP commandline options.

    Patch was tested on following architectures:
    alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k, s390

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

15 Oct, 2007

1 commit

  • The variable CFLAGS is a wellknown variable and the usage by
    kbuild may result in unexpected behaviour.
    On top of that several people over time has asked for a way to
    pass in additional flags to gcc.

    This patch replace use of CFLAGS with KBUILD_CFLAGS all over the
    tree and enabling one to use:
    make CFLAGS=...
    to specify additional gcc commandline options.

    One usecase is when trying to find gcc bugs but other
    use cases has been requested too.

    Patch was tested on following architectures:
    alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k

    Test was simple to do a defconfig build, apply the patch and check
    that nothing got rebuild.

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

22 Jun, 2006

1 commit


06 Mar, 2006

1 commit

  • The kbuild system takes advantage of an incorrect behavior in GNU make.
    Once this behavior is fixed, all files in the kernel rebuild every time,
    even if nothing has changed. This patch ensures kbuild works with both
    the incorrect and correct behaviors of GNU make.

    For more details on the incorrect behavior, see:

    http://lists.gnu.org/archive/html/bug-make/2006-03/msg00003.html

    Changes in this patch:
    - Keep all targets that are to be marked .PHONY in a variable, PHONY.
    - Add .PHONY: $(PHONY) to mark them properly.
    - Remove any $(PHONY) files from the $? list when determining whether
    targets are up-to-date or not.

    Signed-off-by: Paul Smith
    Signed-off-by: Sam Ravnborg

    Paul Smith
     

09 Jan, 2006

1 commit

  • This was causing some ordering problems. Remove the up-front evaluation
    and just revaluate the compiler version each time we need it.

    (The up-front evaluation was problematic because some architectures modify
    the value of $(CC)).

    Signed-off-by: Andrew Morton
    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

13 Sep, 2005

1 commit


12 Sep, 2005

1 commit

  • When introducing the generic asm-offsets.h support the dependency
    chain for the prepare targets was changed. All build scripts expecting
    include/asm/asm-offsets.h to be made when using the prepare target would broke.
    With the limited number of prepare targets left in arch Makefiles
    the trivial solution was to introduce a new arch specific target: archprepare

    The dependency chain looks like this now:

    prepare
    |
    +--> prepare0
    |
    +--> archprepare
    |
    +--> scripts_basic
    +--> prepare1
    |
    +---> prepare2
    |
    +--> prepare3

    So prepare 3 is processed before prepare2 etc.
    This guaantees that the asm symlink, version.h, scripts_basic
    are all updated before archprepare is processed.

    prepare0 which build the asm-offsets.h file will need the
    actions performed by archprepare.

    The head target is now named prepare, because users scripts will most
    likely use that target, but prepare-all has been kept for compatibility.
    Updated Documentation/kbuild/makefiles.txt.

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

10 Sep, 2005

1 commit


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds