Opened 4 years ago
Closed 21 months ago
#60822 closed defect (fixed)
python portgroup doesn't use configure.cflags, configure.cxxflags, configure.ldflags
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | jmroot (Joshua Root) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.6.2 |
| Keywords: | portgroup | Cc: | jmroot (Joshua Root), reneeotten (Renee Otten) |
| Port: | python |
Description
As far as I can tell, the python portgroup doesn't use configure.cflags or configure.cxxflags, making it impossible for a port to add flags when needed.
Change History (5)
comment:1 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | jmroot added |
|---|---|
| Summary: | python portgroup doesn't use configure.cflags or configure.cxxflags → python portgroup doesn't use configure.cflags, configure.cxxflags, configure.ldflags |
comment:2 Changed 2 years ago by mascguy (Christopher Nielsen)
| Keywords: | portgroup added |
|---|
Add keyword portgroup, to pg-related tickets
comment:3 Changed 2 years ago by mascguy (Christopher Nielsen)
| Cc: | reneeotten added |
|---|
Adding @reneeotten to the mix
comment:4 Changed 21 months ago by jmroot (Joshua Root)
Well-behaved python modules usually don't need any additional flags added. The portgroup was designed such that you can turn off its setting of environment variables entirely if need be, and set them to whatever you want. Anyway, I added some variables to make doing it the way you want to easier.
comment:5 Changed 21 months ago by jmroot (Joshua Root)
| Owner: | set to jmroot |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I keep running into this problem.
Also configure.ldflags.
The portgroup sets cflags, cxxflags, ldflags, but to its own values containing the arch flags and sdk flags but no other flags that the port might wish to augment.
Does anybody know why the portgroup was designed this way?