Opened 6 years ago

Last modified 6 years ago

#10874 new bug

Not all non-packaged directories are created by default

Reported by: waddlesplash Owned by: bonefish
Priority: normal Milestone: Unscheduled
Component: Build System Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


Example: /system/non-packaged/bin/x86 does not exist on an "x86gcc2h" system. It can be created with make and then it works fine, but it should be there automatically. In fact, most hybrid directories are missing. Same goes for ~/config/non-packaged/.

Change History (5)

comment:1 by pulkomandy, 6 years ago

The bin one isn't really needed, putting the binaries in the bin/ folder will work just as well. We added the dir to the packaged side only to allow installing gcc2 and gcc4 versions of the same binary side by side.

We still need them for lib and add-ons, however. Are these also missing?

comment:2 by waddlesplash, 6 years ago

At least for the lib directory, yes.

comment:3 by waddlesplash, 6 years ago

Milestone: R1R1/alpha5

comment:4 by pulkomandy, 6 years ago

Milestone: R1/alpha5R1/beta1

comment:5 by pulkomandy, 6 years ago

Component: File SystemsBuild System
Milestone: R1/beta1Unscheduled
Owner: changed from nobody to bonefish

I'm not sure how to create those, it should probably happen in build/jam/images/definitions/common-tail but we need to detect that a secondary arch is being used, and which is it. I'm not sure how to get that information from the ArchitectureRules.

Note: See TracTickets for help on using tickets.