From: Shawn Starr <shawn.starr@rogers.com>
To: Chris Jones <chrisjones@spin.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: No longer able to build kernel into RPM on Fedora
Date: Sat, 12 Oct 2013 21:12:30 -0400 [thread overview]
Message-ID: <1934042.ubj0gKsRvQ@segfault.sh0n.net> (raw)
In-Reply-To: <5259EABD.3060304@spin.net.au>
On Sunday, October 13, 2013 10:35:09 AM Chris Jones wrote:
> As a temporary work around, can you revert to the older version of RPM?
>
Hi Chris,
I was missing rpm-build, I have a patch submitted to force use of rpm-build.
AFAIK, nobody uses legacy rpm anymore since falling back to just rpm will fail
since it does not have --target or -ta options.
Thanks,
Shawn
>
> Regards
>
> On 10/13/2013 05:03 AM, Shawn Starr wrote:
> > Hello folks,
> >
> > My usual approach to testing git snapshots of Linus's tree (with custom
> > patches applied on top) is to make rpm and install this into my system for
> > a clean add/remove of test kernels.
> >
> > However, the developers of rpm removed the --target and -ta options, so I
> > can't take tarball and build into RPM anymore.
> >
> > Since I last built custom RPM builds of Linus's tree was likely Fedora 18,
> > it seems the option target got removed by 19.
> >
> > Any ideas, fixes?
> >
> > Thanks,
> > Shawn
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2013-10-13 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 19:03 Shawn Starr
2013-10-12 19:39 ` [PATCH][BUILD] Force check for rpm-build where package is not installed Shawn Starr
2013-10-12 19:42 ` resend " Shawn Starr
2013-10-13 0:35 ` No longer able to build kernel into RPM on Fedora Chris Jones
2013-10-13 1:12 ` Shawn Starr [this message]
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=1934042.ubj0gKsRvQ@segfault.sh0n.net \
--to=shawn.starr@rogers.com \
--cc=chrisjones@spin.net.au \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®