[Buildroot] Package haserl does not install to root filesystem

[Buildroot] Package haserl does not install to root filesystem

[hartleys]

Hello all,

I have the haserl package selected (due to webif) but it does not get
installed when I do a make.

After the initial make is complete and the root filesystem exists in my
$(TARGET_DIR) I can do the following to get it to install:

$ make haserl-dirclean
$ make

Any ideas how to fix it?

Also, I'm not sure it matters but, the haserl.mk looks different than
most the other .mk that use AUTOTARGETS. It uses := instead of = to set
all the variables.

The ethtool, lighttpd, strace, and which packages are setup similarly.

Thanks,
Hartley

[Buildroot] Package haserl does not install to root filesystem

[Peter Korsgaard]

>>>>> "hartleys" == hartleys  <hartleys@visionengravers.com> writes:

 hartleys> Hello all,

 hartleys> I have the haserl package selected (due to webif) but it
 hartleys> does not get installed when I do a make.

 hartleys> After the initial make is complete and the root filesystem
 hartleys> exists in my $(TARGET_DIR) I can do the following to get it
 hartleys> to install:

 hartleys> $ make haserl-dirclean
 hartleys> $ make

 hartleys> Any ideas how to fix it?

Could you be a bit more specific? Does it error out or does the haserl
install step never run? It seems to work here.

 hartleys> Also, I'm not sure it matters but, the haserl.mk looks
 hartleys> different than most the other .mk that use AUTOTARGETS. It
 hartleys> uses := instead of = to set all the variables.

That's afaik ok. := is more efficient than = so it should normally be
used.

-- 
Bye, Peter Korsgaard

[Buildroot] Package haserl does not install to root filesystem

[hartleys]

On Wednesday, August 13, 2008 12:01 PM, Peter Korsgaard wrote:
>> I have the haserl package selected (due to webif) but it
>> does not get installed when I do a make.
>>
>> After the initial make is complete and the root filesystem
>> exists in my $(TARGET_DIR) I can do the following to get it
>> to install:
>>
>> $ make haserl-dirclean
>> $ make
>>
>> Any ideas how to fix it?
>
> Could you be a bit more specific? Does it error out or does
> the haserl install step never run? It seems to work here.

For the initial make with the root filesystem not existing in
$(TARGET_DIR) but haserl is in $(BUILD_DIR) the build completes with no
errors but haserl is not installed. Actually, none of the
Makefile.autotools.in steps run for haserl.

The "make haserl-dirclean; make" will then do all the steps in
Makefile.autotools.in and install haserl.

I think the problem is because of $(BUILD_DIR)/%/.stamp_target_installed
still existing.

>> Also, I'm not sure it matters but, the haserl.mk looks
>> different than most the other .mk that use AUTOTARGETS. It
>> uses := instead of = to set all the variables.
>
> That's afaik ok. := is more efficient than = so it should
> normally be used.

Not a problem. It just was different so thought I would ask.

Hartley Sweeten

[Buildroot] Package haserl does not install to root filesystem

[Hans-Christian Egtvedt]

On Wed, 2008-08-13 at 15:18 -0400, hartleys wrote:
> On Wednesday, August 13, 2008 12:01 PM, Peter Korsgaard wrote:
> >> I have the haserl package selected (due to webif) but it
> >> does not get installed when I do a make.
> >>
> >> After the initial make is complete and the root filesystem
> >> exists in my $(TARGET_DIR) I can do the following to get it
> >> to install:
> >>
> >> $ make haserl-dirclean
> >> $ make
> >>
> >> Any ideas how to fix it?
> >
> > Could you be a bit more specific? Does it error out or does
> > the haserl install step never run? It seems to work here.
> 
> For the initial make with the root filesystem not existing in
> $(TARGET_DIR) but haserl is in $(BUILD_DIR) the build completes with no
> errors but haserl is not installed. Actually, none of the
> Makefile.autotools.in steps run for haserl.
> 
> The "make haserl-dirclean; make" will then do all the steps in
> Makefile.autotools.in and install haserl.
> 
> I think the problem is because of $(BUILD_DIR)/%/.stamp_target_installed
> still existing.
>

I submitted a fix for this some time back, but it is still hanging in
limbo.

http://buildroot.uclibc.org/lists/buildroot/2008-July/009930.html

All packages using autotools will need to be updated to take advantage
of the change though. See the popt example in the email URL.