All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <xfs@tlinx.org>
To: Peter Shuere <petershuere@yahoo.com>
Cc: xfs@oss.sgi.com
Subject: Re: Building XFSDump but missing uuid development package
Date: Sat, 01 May 2010 06:38:52 -0700	[thread overview]
Message-ID: <4BDC2EEC.9080808@tlinx.org> (raw)
In-Reply-To: <53964.41414.qm@web180401.mail.gq1.yahoo.com>



Peter Shuere wrote:
> Hi,
> 
> I am trying to build the XFS utility, but during the build-process, I ran into a problem saying that I need the UUID development package to make the build complete. I am using OpenSUSE 11.2, where should I get the copy of the uuid-devel source (or binary, whichever one that works).
(On SuSE 11.2:)
> zypper se uuid 
Loading repository data...
Reading installed packages...

S | Name                | Summary                                   | Type      
--+---------------------+-------------------------------------------+-----------
i | libuuid-devel       | Development files for libuuid1            | package   
  | libuuid-devel-32bit | Development files for libuuid1            | package   
i | libuuid1            | Library to generate UUIDs                 | package   
i | libuuid1-32bit      | Library to generate UUIDs                 | package   
  | perl-Data-UUID      | Perl extension for generating Globally/-> | package   
  | perl-Data-UUID      | Perl extension for generating Globally/-> | srcpackage
  | uuidd               | Utilities for the Second Extended File -> | package   
---
Does libuuid-devel not work for you?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2010-05-01 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30 16:18 Building XFSDump but missing uuid development package Peter Shuere
2010-04-30 16:49 ` Eric Sandeen
2010-05-01 13:38 ` Linda Walsh [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=4BDC2EEC.9080808@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=petershuere@yahoo.com \
    --cc=xfs@oss.sgi.com \
    /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.