#12119 closed bug (invalid)
Cannot build x86 packages in hybrid system with haikuporter
| Reported by: | haiqu | Owned by: | bonefish |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Build System | Version: | R1/Development |
| Keywords: | haukuporter | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This is the wrong place to report but since I can't access haikuports site with either WebPositive or BeZilla it will have to do. (Ref: ticket #12013)
A few days ago I updated haikuporter and haikuports git repositories and a major change occurred. All packages built with the _x86 extension (eg GCC4 packages) were moved to haikuports/packages/.obsolete and I can no longer build for this target.
This is severely hampering development of some fairly complex stuff I'm working on, so I'd like the change reverted or a REALLY good reason why it was changed. Thanks.
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Reported at the wrong place, sorry, it won't do.
follow-up: 4 comment:3 by , 9 years ago
Since I have innumerable bug reports relating to packages being stored in HaikuPorts, and since my copy of HaikuPorter has now stopped working with a ridiculous* error, perhaps you could let me know where I'm supposed to report such issues.
I did finally manage to log in to BitBucket (from WinXP) but there doesn't seem to be any way to communicate to the members who, in any case, are the same people developing Haiku.
* requires "lib:libjpeg >= 9.1.0" of package "tiff-3.9.6-2" could not be resolved
I get this no matter what I try to build now. There is no libjpeg 9.1.0
comment:4 by , 9 years ago
Replying to haiqu:
There is no libjpeg 9.1.0
Yes, there is: https://bitbucket.org/haikuports/haikuports/src/67cbec5bd1f89312a73236a09aaefe624a338b29/media-libs/jpeg/jpeg-9a.recipe?at=master
I did finally manage to log in to BitBucket (from WinXP) but there doesn't seem to be any way to communicate to the members who, in any case, are the same people developing Haiku.
Why do you need to communicate with people who are both Haiku and HaikuPorts developers? HaikuPorter and HaikuPorts are not affiliated with Haiku project. The fact that there are people who are Haiku developers is coincidence (well, not exactly, but I hope you get my point).
Bug reports should go to their respective bug trackers.
Configuration error. config/settings/haikuports.conf had the line:
#SECONDARY_TARGET_ARCHITECTURES="x86"
Note that it's commented out. The result was fairly confusing.