From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10886] New: openssl-1.0.2n fails to build
Date: Wed, 21 Mar 2018 08:17:07 +0000 [thread overview]
Message-ID: <bug-10886-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10886
Bug ID: 10886
Summary: openssl-1.0.2n fails to build
Product: buildroot
Version: 2018.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: seregajsv at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7551
--> https://bugs.busybox.net/attachment.cgi?id=7551&action=edit
Fixed 0001-Dont-waste-time-building-manpages-if-we-re-not-going.patch
When applying 0001-Dont-waste-time-building-manpages-if-we-re-not-going.patch
occurs error:
patching file Makefile.org
Hunk #1 FAILED at 527.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.org.rej
I fixed this problem for myself. Please, see attachment.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-03-21 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 8:17 bugzilla at busybox.net [this message]
2018-03-21 17:54 ` [Buildroot] [Bug 10886] openssl-1.0.2n fails to build bugzilla at busybox.net
2018-04-01 9:20 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-10886-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox