From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: cruft left over from "make uninstall" [was: failed to build bzr head on powerpc (ieee1275)]
Date: Wed, 22 Feb 2012 16:28:21 +0100 [thread overview]
Message-ID: <4F450995.8040306@gmail.com> (raw)
In-Reply-To: <4F445A7B.9050209@fifthhorseman.net>
Fixed
On 22.02.2012 04:01, Daniel Kahn Gillmor wrote:
> On 02/21/2012 09:30 PM, Mike Gilbert wrote:
>> I ran into that myself this weekend. Solution: regenerate POTFILES.in.
>>
>> find . -name '*.c' -print | sort> po/POTFILES.in
> Thanks, that did indeed let the build complete.
>
> i completed building it as a non-privileged user, and then as the
> superuser, i did:
>
> make install
> make uninstall
>
> That appears to have left a few files in /usr/local that i think it
> shouldn't have. I think the uninstall target might have drifted a bit:
>
> 0 root@hollywood:/home/dkg/src/grub/grub# find /usr/local/ | grep grub
> /usr/local/lib/grub
> /usr/local/lib/grub/powerpc-ieee1275
> /usr/local/etc/grub.d
> /usr/local/share/grub
> /usr/local/share/grub/widthspec.h
> /usr/local/share/grub/ascii.pf2
> /usr/local/share/grub/unicode.pf2
> /usr/local/share/grub/euro.pf2
> /usr/local/share/grub/ascii.h
> 0 root@hollywood:/home/dkg/src/grub/grub#
>
> --dkg
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
prev parent reply other threads:[~2012-02-22 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 23:38 failed to build bzr head on powerpc (ieee1275) Daniel Kahn Gillmor
2012-02-22 2:30 ` Mike Gilbert
2012-02-22 3:01 ` cruft left over from "make uninstall" [was: failed to build bzr head on powerpc (ieee1275)] Daniel Kahn Gillmor
2012-02-22 3:23 ` Mike Gilbert
2012-02-22 3:45 ` Daniel Kahn Gillmor
2012-02-22 15:28 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=4F450995.8040306@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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.