Opened 11 years ago
Closed 3 years ago
#40408 closed update (fixed)
dwarf @0.3.0_0: update to 0.3.1
| Reported by: | xnando@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | haspatch maintainer | Cc: | ryandesign (Ryan Carsten Schmidt) |
| Port: | dwarf |
Description
-- a little and powerful object file manipulation tool.
new version 0.3.1 fixes some bugs
Attachments (3)
Change History (17)
comment:1 Changed 11 years ago by raimue (Rainer Müller)
comment:2 Changed 11 years ago by mf2k (Frank Schima)
| Type: | submission → update |
|---|---|
| Version: | 2.2.0 |
comment:4 Changed 11 years ago by mf2k (Frank Schima)
We also request that you make whitespace changes in a different patch. It's very hard to tell what you have changed. However, I can already see that the revision line needs to be deleted as with all version increases.
Changed 11 years ago by xnando@…
| Attachment: | Portfile-dwarf.diff added |
|---|
sysutils/dwarf version 0.3.1 diff Portfile
comment:6 follow-up: 8 Changed 11 years ago by mf2k (Frank Schima)
There are still lots of whitespace changes but the real changes can be observed more easily now. What is the purpose of the no-as-needed variant? That name is not very good. I'm not sure we even need to support building on Linux. Macports does not currently run on it as far as I know.
comment:7 Changed 11 years ago by mf2k (Frank Schima)
Also the maintainer email was changed. Is this your new email address?
comment:8 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to macsforever2000@…:
What is the purpose of the no-as-needed variant? That name is not very good.
If -Wl,--no-as-needed needs to be passed on Linux and not on OS X, it should probably just go in a platform linux block instead of a variant. It should also be set using configure.ldflags, unless the configure script doesn’t correctly respect its environment.
I'm not sure we even need to support building on Linux. MacPorts does not currently run on it as far as I know.
Base does run on Linux; I think the pregenerated indexes are created on Linux. Building ports is an entirely different story, of course.
comment:9 Changed 9 years ago by larryv (Lawrence Velázquez)
| Keywords: | haspatch maintainer added |
|---|---|
| Owner: | changed from macports-tickets@… to larryv@… |
| Status: | new → assigned |
| Summary: | dwarf → dwarf @0.3.0_0: update to 0.3.1 |
Changed 9 years ago by larryv (Lawrence Velázquez)
| Attachment: | dwarf.main.log added |
|---|
failed build on Yosemite
comment:10 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign added |
|---|
I fixed all the build failures in 0.3.0 in [86310cfff25add9f384f44e928b720b568b96d67/macports-ports].
The ChangeLog says 0.3.1 only changed some build system problems, so the end result that gets installed would be no different than 0.3.0, so there is no pressing need to update to 0.3.1. 0.3.1 does not build due to:
make[4]: *** No rule to make target `dwarfrc', needed by `all-am'. Stop.
comment:11 Changed 7 years ago by l2dy (Zero King)
0.3.2 was released at https://github.com/elboza/dwarf-ng/releases/tag/dwarf-0.3.2.
comment:12 Changed 7 years ago by raimue (Rainer Müller)
| Owner: | changed from larryv to fernando.iazeolla@… |
|---|
comment:13 Changed 5 years ago by kurthindenburg (Kurt Hindenburg)
| Owner: | fernando.iazeolla@… deleted |
|---|
comment:14 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | set to ryandesign |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Please attach port updates as unified diff as described in the guide. This makes it easier to review changes.