Skip to contentSkip to conversation

New: liblockfile fails to install due to missing directories

Buildroot bugzilla at busybox.net 1 participant 2 messages Feb 2, 2009

lore
Share & tools
lore
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=85

Host: pc-linux
Target: arm-linux-gnueabi (gcc 4.2.2)
Build: 2009.02-rc3
Summary: liblockfile fails to install due to missing directories
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: hunter.cobbs at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0

install -m 644 lockfile.h maillock.h /home/hcobbs/dev/src/buildroot-2009.02-rc3/ucm_build_arm/staging_dir/usr/local/include
install: target `/home/hcobbs/dev/src/buildroot-2009.02-rc3/ucm_build_arm/staging_dir/usr/local/include' is not a directory
make[1]: *** [install_common] Error 1

---------------------------------

also occurs for man1/man3

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 85] liblockfile fails to install due to missing directories

https://bugs.busybox.net/show_bug.cgi?id=85

Peter Korsgaard <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |jacmet at uclibc.org
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME

--- Comment #1 from Peter Korsgaard <[email protected]> 2009-02-02 21:38:49 UTC --- Again, it works here with the default internal toolchain:

install -m 644 lockfile.h maillock.h
/tmp/br/arm/build_arm/staging_dir/usr/include

Strange that it would use the usr/local prefix for you.

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.