backports.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Doyle <wpdster@gmail.com>
To: Steve deRosier <derosier@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>, backports@vger.kernel.org
Subject: Re: How to use backports?
Date: Wed, 16 May 2018 09:24:58 -0400	[thread overview]
Message-ID: <CAF_dkJAe8m+BibjxQuTgapHCZAG436x8g+UPRkr7ra44-xccXg@mail.gmail.com> (raw)
In-Reply-To: <CALLGbRL915L0uTyJnhD7eQFy2aBgQzRQMW_XiLgfypmbW-sHvw@mail.gmail.com>

On Tue, May 15, 2018 at 6:19 PM, Steve deRosier <derosier@gmail.com> wrote:
> On Tue, May 15, 2018 at 1:31 PM Johannes Berg <johannes@sipsolutions.net>
> wrote:
> I usually run Ubuntu LTS (server, not desktop) for most of my Linux build
> systems. Like Johannes mentioned, I build coccinelle from source.  While
> I'm aware of the >= 1.0.6 patch that went in a few days ago, I haven't
> built with anything that modern yet. Fact is, since changing jobs recently,
> I'm not using backports as much as I used to since I'm stuck working on a
> vendor driver.
>
> Anyway, sorry I'm not that much help - I just wanted to answer your "does
> anyone use Ubuntu for backports building" question.  Answer is yes, it's
> possible to do so.
Thanks Steve.  That is a help.
I was just trying to decide if I should return from interrupt, or
declare a fault :-)

When too many things started going wrong (didn't have coccinelle
installed, have never heard of it, have no idea what it is, apt-get
installed it, was informed it was too old, git cloned it, installed
dependencies for building it, found that it would not compile, even
with the dependencies installed), the "too hard" LED came on and I
figured I should ask some questions.  I'll go find somebody I can ask
about compiling coccinelle (whatever that is) on Ubuntu 16.04, figure
out what's going on there, and return from interrupt now.

Then I'll either figure out what's going on with the --integrate flag
in backports, or decide to live with a loadable module.

Thanks for the help.

--wpd
--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2018-05-16 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 19:41 How to use backports? Patrick Doyle
2018-05-15 20:04 ` Johannes Berg
2018-05-15 20:26   ` Patrick Doyle
2018-05-15 20:30     ` Johannes Berg
2018-05-15 22:19       ` Steve deRosier
2018-05-16 13:24         ` Patrick Doyle [this message]
2018-05-16 13:26           ` Johannes Berg
2018-05-16 13:28             ` Patrick Doyle

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=CAF_dkJAe8m+BibjxQuTgapHCZAG436x8g+UPRkr7ra44-xccXg@mail.gmail.com \
    --to=wpdster@gmail.com \
    --cc=backports@vger.kernel.org \
    --cc=derosier@gmail.com \
    --cc=johannes@sipsolutions.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;
as well as URLs for NNTP newsgroup(s).