All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org, dwmw2@infradead.org,
	linux-next@vger.kernel.org, linux-m68k@lists.linux-m68k.org
Subject: Re: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Wed, 18 Mar 2009 13:12:00 -0500	[thread overview]
Message-ID: <200903181312.02047.rob@landley.net> (raw)
In-Reply-To: <49C087F3.3080507@snapgear.com>

On Wednesday 18 March 2009 00:34:43 Greg Ungerer wrote:
> Hi Rob,
>
> Rob Landley wrote:
> > On Monday 16 March 2009 18:10:45 Greg Ungerer wrote:
> >>>>    git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
> >>>> fix-includes
...
> > What _should_ I have done?
>
> The git clone you have done will just get the master branch,
> and put it in a directory named fix-includes.
>
> Which is ok, but you still won't have the "fix-includes" branch.
> Do this after the clone:
>
>    git pull
> git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
> fix-includes

Ah, that did something interesting...  And the resulting headers built in 
uClibc.  (Works for me!)

confirmed-uClibc-builds-with-it-by: Rob Landley <rob@landley.net>

Thanks,

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org, dwmw2@infradead.org,
	linux-next@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: Re: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Wed, 18 Mar 2009 13:12:00 -0500	[thread overview]
Message-ID: <200903181312.02047.rob@landley.net> (raw)
In-Reply-To: <49C087F3.3080507@snapgear.com>

On Wednesday 18 March 2009 00:34:43 Greg Ungerer wrote:
> Hi Rob,
>
> Rob Landley wrote:
> > On Monday 16 March 2009 18:10:45 Greg Ungerer wrote:
> >>>>    git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
> >>>> fix-includes
...
> > What _should_ I have done?
>
> The git clone you have done will just get the master branch,
> and put it in a directory named fix-includes.
>
> Which is ok, but you still won't have the "fix-includes" branch.
> Do this after the clone:
>
>    git pull
> git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
> fix-includes

Ah, that did something interesting...  And the resulting headers built in 
uClibc.  (Works for me!)

confirmed-uClibc-builds-with-it-by: Rob Landley <rob@landley.net>

Thanks,

Rob

  parent reply	other threads:[~2009-03-18 18:12 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12  9:37 make headers_install broken for ARCH=m68k in 2.6.29-rc7 Rob Landley
2009-03-12  9:58 ` Sam Ravnborg
2009-03-12 20:03   ` Rob Landley
2009-03-12 20:58     ` Sam Ravnborg
2009-03-12 23:24       ` Stephen Rothwell
2009-03-12 21:02     ` Sam Ravnborg
2009-03-12 22:40       ` Geert Uytterhoeven
2009-03-13  3:25         ` Rob Landley
2009-03-13  7:04           ` Greg Ungerer
2009-03-13  8:25             ` Sam Ravnborg
2009-03-13  8:33               ` Geert Uytterhoeven
2009-03-13  8:59                 ` Sam Ravnborg
2009-03-13 10:52                   ` Greg Ungerer
2009-03-13 12:14                     ` Geert Uytterhoeven
2009-03-13 12:14                       ` Geert Uytterhoeven
2009-03-16 12:40                       ` Greg Ungerer
2009-03-16 12:40                       ` Greg Ungerer
2009-03-16 12:40                         ` Greg Ungerer
2009-03-16 20:20                         ` Rob Landley
2009-03-16 20:20                         ` Rob Landley
2009-03-16 20:20                           ` Rob Landley
2009-03-16 22:08                           ` Geert Uytterhoeven
2009-03-16 23:09                             ` Greg Ungerer
2009-03-16 23:10                           ` Greg Ungerer
2009-03-16 23:10                             ` Greg Ungerer
2009-03-18  4:03                             ` Rob Landley
2009-03-18  4:03                               ` Rob Landley
2009-03-18  5:34                               ` Greg Ungerer
2009-03-18  5:34                                 ` Greg Ungerer
2009-03-18 18:12                                 ` Rob Landley
2009-03-18 18:12                                 ` Rob Landley [this message]
2009-03-18 18:12                                   ` Rob Landley
2009-03-18 23:53                                   ` Greg Ungerer
2009-03-18 23:53                                     ` Greg Ungerer
2009-03-18 23:53                                   ` Greg Ungerer
2009-03-19  7:59                                   ` Geert Uytterhoeven
2009-03-19  7:59                                     ` Geert Uytterhoeven
2009-03-19  8:41                                     ` Rob Landley
2009-03-18  5:34                               ` Greg Ungerer
2009-03-13  8:25           ` Geert Uytterhoeven
2009-03-13  6:53         ` Greg Ungerer
2009-04-01 16:57 ` Lennart Sorensen
2009-04-01 19:03   ` Sam Ravnborg
2009-04-01 19:48     ` Lennart Sorensen
2009-04-01 20:23       ` Geert Uytterhoeven
2009-04-01 22:59         ` Lennart Sorensen
2009-04-02  2:14           ` Rob Landley
2009-04-02 21:59             ` Lennart Sorensen
2009-04-03  0:24               ` Rob Landley
2009-04-03  4:10                 ` Lennart Sorensen

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=200903181312.02047.rob@landley.net \
    --to=rob@landley.net \
    --cc=dwmw2@infradead.org \
    --cc=geert@linux-m68k.org \
    --cc=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.