Opened 11 years ago
Last modified 8 years ago
#5611 new Library Submissions
bjam: define the right OS name on Hurd
Reported by: | Owned by: | Eric Niebler | |
---|---|---|---|
Milestone: | Website 1.X | Component: | xpressive |
Version: | Boost.Build-M3 | Severity: | Not Applicable |
Keywords: | Cc: |
Description
Report from Pino Toscano (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630652):
Currently bjam does not identify Hurd when using e.g. os.name in jam scripts:
$ bjam -v | head -n1 Boost.Jam Version 3.1.19. OS=UNKNOWN.
The attached patch (which should be suitable for upstream inclusion) sets the correct #define's for Hurd in bjam, adding also the path detection for the bjam test suite.
$ bjam -v | head -n1 Boost.Jam Version 3.1.19. OS=HURD.
Attachments (1)
Change History (4)
by , 11 years ago
Attachment: | hurd-bjam_os.patch added |
---|
follow-up: 2 comment:1 by , 11 years ago
comment:2 by , 11 years ago
Replying to vladimir_prus:
It seems to me that while this patch appears safe, it is of limited utility, because builtin.jam does not know about Hurd either.
Do you mean os.names in both builtin.jam and builtin.py?
comment:3 by , 8 years ago
Component: | Building Boost → xpressive |
---|---|
Milestone: | To Be Determined → Website 1.X |
Owner: | set to |
Severity: | Problem → Not Applicable |
Type: | Patches → Library Submissions |
Version: | Boost 1.46.1 → Boost.Build-M3 |
Wow, superb blog layout! How long have you been blogging for? you made blogging look easy. The overall look of your website is wonderful, let alone the content! daefbfdfeakcgbge
It seems to me that while this patch appears safe, it is of limited utility, because builtin.jam does not know about Hurd either. Am I mistaken, or there are more patches in the queue?