Opened 17 years ago
Closed 8 years ago
#4118 closed defect (wontfix)
Detection for boost versions
| Reported by: | Owned by: | lasgouttes | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | build | Version: | 1.5.1 |
| Severity: | normal | Keywords: | patch |
| Cc: |
Description (last modified by )
Using external boost libraries < 1.34 fails to compile with 1.5.1, due to lack
of things like boost::filesystem::lookup_error and the location of
boost::filesystem::filesystem_error.
Attachments (1)
Change History (13)
by , 17 years ago
| Attachment: | boost-1.34.patch added |
|---|
comment:1 by , 17 years ago
| Keywords: | patch added |
|---|---|
| Milestone: | → 1.5.2 |
comment:2 by , 17 years ago
We do not plan to support boost < 1.34. We will try however to support
boost >=1.34 for the future.
I will try to come up with some tests for boost, but simpler than these probably.
comment:3 by , 17 years ago
| Milestone: | 1.5.2 → 1.5.x |
|---|
comment:4 by , 16 years ago
| Milestone: | 1.5.x → 1.6.x |
|---|
1.5.x is frozen. Shifting all 1.5.x-targetted bugs to 1.6.x.
If you have reported this bug, please verify if it still occurs in 1.6.0 and
close the report, if not.
comment:5 by , 16 years ago
As far as I can see, Lyx configure still has *no* checks for which boost version
is being used when an external boost is used to compile, and so this bug is
probably still there.
comment:6 by , 15 years ago
| Summary: | External boost < 1.34 fails to compile → Detection for boost versions |
|---|
comment:7 by , 15 years ago
| Priority: | high → normal |
|---|
comment:8 by , 13 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | 1.6.x → 2.0.x |
How hard is it to fix this?
comment:9 by , 10 years ago
| Milestone: | 2.0.x → 2.1.x |
|---|
LyX 2.0.8 is released, so all 2.0.x bugs are being retargeted to 2.1.x. If this is your bug, please check whether the 2.1.x milestone makes sense and, if not, remove it.
comment:10 by , 8 years ago
| Milestone: | 2.1.x → 2.2.x |
|---|
Moving all 2.1.x bugs to 2.2.x. Feel free to triage....
comment:11 by , 8 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
I'm going to close this bug as WONTFIX, since it clearly is not going to get fixed. We are moving towards eliminating the dependency on boost, anyway.
comment:12 by , 6 years ago
| Milestone: | 2.2.x |
|---|
Check boost version