[Buildroot] make -C <buildroot_directory> failed

[Buildroot] make -C <buildroot_directory> failed

[Matthew Davison]

Attempting to invoke the top level buildroot makefile from a higher
level Makefile or simply with make -C <buildroot_directory> fails during
the kernel build. This is even true if 'make -C .' is invoked from the
top level buildroot directory, as long as a kernel build is enabled. It
appears that the problem has something to do with make's
"Entering/Leaving directory" messages, as the output below suggests.
When I passed the --no-print-directory option to make, I was able to
build without problems.
 
Below is the output from my failed build.
 
  INSTALL
/home/lars/mdavison/buildroot-2009.11/output/target/lib/firmware/sb16/im
a_adpcm_init.csp
  INSTALL
/home/lars/mdavison/buildroot-2009.11/output/target/lib/firmware/sb16/im
a_adpcm_playback.csp
  INSTALL
/home/lars/mdavison/buildroot-2009.11/output/target/lib/firmware/sb16/im
a_adpcm_capture.csp
  DEPMOD  2.6.30.2
make[1]: Leaving directory
`/home/lars/mdavison/buildroot-2009.11/output/build/linux-2.6.30.2'
WARNING: Can't read module make[1]:: No such file or directory
WARNING: Can't read module Entering: No such file or directory
WARNING: Can't read module directory: No such file or directory
WARNING: Can't read module
`/home/lars/mdavison/buildroot-2009.11/output/build/linux-2.6.30.2': No
such file or directory
WARNING: Can't read module 2.6.30.2: No such file or directory
WARNING: Can't read module make[1]:: No such file or directory
WARNING: Can't read module Leaving: No such file or directory
WARNING: Can't read module directory: No such file or directory
WARNING: Can't read module
`/home/lars/mdavison/buildroot-2009.11/output/build/linux-2.6.30.2': No
such file or directory
FATAL: Could not open
/home/lars/mdavison/buildroot-2009.11/output/target/lib/modules/2.6.28-1
5-generic/modules.dep.temp for writing: No such file or directory
make: ***
[/home/lars/mdavison/buildroot-2009.11/output/stamps/linux_modules_targe
t_installed] Error 1
make: Leaving directory `/home/lars/mdavison/buildroot-2009.11'
 
**********************************************************************
This e-mail is the property of Lantronix. It is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this e-mail, or the information contained herein, to anyone other than the intended recipient is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100223/7858341e/attachment.htm>

[Buildroot] make -C <buildroot_directory> failed

[Peter Korsgaard]

>>>>> "Matthew" == Matthew Davison <matt.davison@lantronix.com> writes:

Hi,

 Matthew> Attempting to invoke the top level buildroot makefile from a
 Matthew> higher level Makefile or simply with make -C
 Matthew> <buildroot_directory> fails during the kernel build. This is
 Matthew> even true if 'make -C .' is invoked from the top level
 Matthew> buildroot directory, as long as a kernel build is enabled. It
 Matthew> appears that the problem has something to do with make's
 Matthew> "Entering/Leaving directory" messages, as the output below
 Matthew> suggests. When I passed the --no-print-directory option to
 Matthew> make, I was able to build without problems.
 
 Matthew> Below is the output from my failed build.
 
 Matthew>   INSTALL /home/lars/mdavison/buildroot-2009.11/output/target/lib/firmware/
 Matthew> sb16/ima_adpcm_init.csp
 Matthew>   INSTALL /home/lars/mdavison/buildroot-2009.11/output/target/lib/firmware/
 Matthew> sb16/ima_adpcm_playback.csp
 Matthew>   INSTALL /home/lars/mdavison/buildroot-2009.11/output/target/lib/firmware/
 Matthew> sb16/ima_adpcm_capture.csp
 Matthew>   DEPMOD  2.6.30.2
 Matthew> make[1]: Leaving directory `/home/lars/mdavison/buildroot-2009.11/output/build
 Matthew> /linux-2.6.30.2'

It looks to be an issue with the makefile of the Linux kernel. Please
post your .config so we can try to reproduce the problem. Do you only
have this issue with 2.6.30, or also other kernel versions? (perhaps
give buildroot-2010.02-rc1 a try)

Remember that you cannot build buildroot with a parallel toplevel make
(-jX).

-- 
Bye, Peter Korsgaard

[Buildroot] make -C <buildroot_directory> failed

[Cameron Hutchison]

"Matthew Davison" <matt.davison@lantronix.com> writes:

>Attempting to invoke the top level buildroot makefile from a higher
>level Makefile or simply with make -C <buildroot_directory> fails during
>the kernel build. This is even true if 'make -C .' is invoked from the
>top level buildroot directory, as long as a kernel build is enabled. It
>appears that the problem has something to do with make's
>"Entering/Leaving directory" messages, as the output below suggests.
>When I passed the --no-print-directory option to make, I was able to
>build without problems.

I think I see the problem. See if this patch fixes it. I haven't tested
this, but this looks right.

[Buildroot] make -C <buildroot_directory> failed

[Peter Korsgaard]

>>>>> "Cameron" == Cameron Hutchison <lists@xdna.net> writes:

 Cameron> "Matthew Davison" <matt.davison@lantronix.com> writes:
 >> Attempting to invoke the top level buildroot makefile from a higher
 >> level Makefile or simply with make -C <buildroot_directory> fails during
 >> the kernel build. This is even true if 'make -C .' is invoked from the
 >> top level buildroot directory, as long as a kernel build is enabled. It
 >> appears that the problem has something to do with make's
 >> "Entering/Leaving directory" messages, as the output below suggests.
 >> When I passed the --no-print-directory option to make, I was able to
 >> build without problems.

 Cameron> I think I see the problem. See if this patch fixes it. I haven't tested
 Cameron> this, but this looks right.

Yes, seems sensible - Committed, thanks.

-- 
Bye, Peter Korsgaard

[Buildroot] make -C <buildroot_directory> failed

[Yann E. MORIN]

Cameron, All,

On Tuesday 23 February 2010 23:00:16 Cameron Hutchison wrote:
> >Attempting to invoke the top level buildroot makefile from a higher
> >level Makefile or simply with make -C <buildroot_directory> fails during
> >the kernel build. This is even true if 'make -C .' is invoked from the
> >top level buildroot directory, as long as a kernel build is enabled. It
> >appears that the problem has something to do with make's
> >"Entering/Leaving directory" messages, as the output below suggests.

Yes, this is expected behavior:
http://www.gnu.org/software/make/manual/make.html#g_t_002dw-Option

Basically, using $(MAKE) has special behavior, which is fortunate most
os the time, but fails for this specific case, where the second 'make'
is completely decorelated (Makefile-wise) from the calling 'make'.

> >When I passed the --no-print-directory option to make, I was able to
> >build without problems.
> I think I see the problem. See if this patch fixes it. I haven't tested
> this, but this looks right.

I'd say that is the correct fix.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'

[Buildroot] make -C <buildroot_directory> failed

[Will Wagner]

On 23/02/2010 22:00, Cameron Hutchison wrote:
> "Matthew Davison"<matt.davison@lantronix.com>  writes:
>
>    
>> Attempting to invoke the top level buildroot makefile from a higher
>> level Makefile or simply with make -C<buildroot_directory>  fails during
>> the kernel build. This is even true if 'make -C .' is invoked from the
>> top level buildroot directory, as long as a kernel build is enabled. It
>> appears that the problem has something to do with make's
>> "Entering/Leaving directory" messages, as the output below suggests.
>> When I passed the --no-print-directory option to make, I was able to
>> build without problems.
>>      
> I think I see the problem. See if this patch fixes it. I haven't tested
> this, but this looks right.
>    

I agree correct fix.

That's the same as the patch I submitted here: 
http://lists.busybox.net/pipermail/buildroot/2010-January/031690.html
> > From 5dbf2e25bbd7d4f4586888384b3c207dd1a6afca Mon Sep 17 00:00:00 2001
> From: Cameron Hutchison<cam@camh.ch>
> Date: Wed, 24 Feb 2010 08:52:44 +1100
> Subject: [PATCH] Fix probing of kernel version
>
> Probing the kernel version uses command substitution to capture the
> result of a make command. If the top-level make is run with -C, the
> sub-make will print entering/leaving directory messages, mucking up the
> output we're trying to capture.
>
> Invoke the sub-make with --no-print-directory so we get clean output.
>
> Signed-off-by: Cameron Hutchison<cam@camh.ch>
> ---
>   target/linux/Makefile.in.advanced |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/target/linux/Makefile.in.advanced b/target/linux/Makefile.in.advanced
> index b4774ca..7679d1e 100644
> --- a/target/linux/Makefile.in.advanced
> +++ b/target/linux/Makefile.in.advanced
> @@ -41,7 +41,7 @@ endif
>   endif
>
>   # Ask the kernel what version number it will use when installing modules
> -LINUX26_VERSION_PROBED = `$(MAKE) $(LINUX26_MAKE_FLAGS) -C $(LINUX26_DIR) -s kernelrelease`
> +LINUX26_VERSION_PROBED = `$(MAKE) $(LINUX26_MAKE_FLAGS) -C $(LINUX26_DIR) --no-print-directory -s kernelrelease`
>
>   ifeq ($(BOARD_PATH),)
>   BOARD_PATH:=$(call qstrip,$(BR2_BOARD_PATH))
>    

[Buildroot] make -C <buildroot_directory> failed

[Peter Korsgaard]

>>>>> "Will" == Will Wagner <will_wagner@carallon.com> writes:

Hi,


 Will> That's the same as the patch I submitted here:
 Will> http://lists.busybox.net/pipermail/buildroot/2010-January/031690.html

Sorry, must have missed that patch. It shouldn't happen, but it does now
and then - Please resend patches or attach to bugzilla issues if it does.

-- 
Bye, Peter Korsgaard