| Summary: | dev-libs/openssl-1.0.0 fails to compile on sparc-fbsd | ||
|---|---|---|---|
| Product: | Gentoo/Alt | Reporter: | Tibor Vago <tibor.vago> |
| Component: | FreeBSD | Assignee: | Gentoo/BSD Team <bsd+disabled> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | tibor.vago |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | Sparc64 | ||
| OS: | FreeBSD | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
openssl-1.0.0e-bsd-sparc64.patch
openssl-1.0.0e-r1.ebuild openssl-1.0.0e.ebuild patch |
||
I'm working on a proper patch and ebuild and will upload here. On sparc64-gentoo-freebsd8.2 ASM options in openssl generate "__sparc_utrap: fatal illegal instruction" message and cause completely unusable system so I modified the ebuild to disable asm option on sparc-fbsd while the problem will fixed. Created attachment 292707 [details, diff]
openssl-1.0.0e-bsd-sparc64.patch
openssl-0.9.8e-bsd-sparc64.patch based and updated
Created attachment 292709 [details]
openssl-1.0.0e-r1.ebuild
Modified ebuild to use the patch and disable asm on sparc-fbsd to prevent "illegal instruction" error.
Please test if possible and commit to the portage tree. Created attachment 294395 [details, diff]
openssl-1.0.0e.ebuild patch
patch for openssl-1.0.0e.ebuild for build on sparc-fbsd
The problem is still in openssl-1.0.0f (In reply to comment #7) > The problem is still in openssl-1.0.0f I can't confirm the problem since I don't have sparc. Please send the source code patch and get response from them. Thanks, Comment on attachment 292707 [details, diff]
openssl-1.0.0e-bsd-sparc64.patch
the removal of -B makes sense (it's a compat no-op). but why the ultrasparc change in the Configure file ?
(In reply to SpanKY from comment #9) IMHO dont waste your time on this bug; sparc-fbsd will need to more or less start from scratch since afaik nobody has been working for this arch since years closing as obsolete |
Missing patch: openssl-0.9.8e-bsd-sparc64.patch Please apply on 1.0.0 versions. It can/could depend on "sparc-fbsd": use sparc-fbsd && epatch "${FILESDIR}"/${PN}-0.9.8e-bsd-sparc64.patch