linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Milind <milind@gslab.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: EXT vs XFS at 80% filled filesystem
Date: Wed, 20 May 2009 11:13:30 +0530	[thread overview]
Message-ID: <1242798210.3457.4.camel@alhena> (raw)
In-Reply-To: <20090518131755.GJ32019@mit.edu>

I am building xfsprogs to add it to my toolchain and want xfsprogs to
refer to my toolchain's libuuid. So I need libuuid.so in my toolchain.
But building e2fsprogs from sources doesn't build libuuid as .so (builds
as .a). Could you please give some pointers on building libuuid as .so?

Do I have to change Makefiles? How do you do it for ubuntu/debian
packages that you maintain?

Thanks in advance
-Miline

On Mon, 2009-05-18 at 09:17 -0400, Theodore Tso wrote:
> On Mon, May 18, 2009 at 06:33:28PM +0530, Milind wrote:
> > Hi Theodore,
> > 
> > I am facing some weird problem of cross compiling libuuid sources. I
> > downloaded e2fsprogs and cross-compiled them but when I do "make
> > install-libs" it doesn't really install libuuid.so but installs
> > libuuid.a.
> 
> The "make install" taret is designed to install what is needed to run
> the e2fsprogs programs, including shared libraries; "make
> install-libs" is designed to install what as needed for development
> purpoes.
> 
> So running "make install" in the lib/uuid" should do what you want.
> 
>    	   	 	     	 	   	  - Ted
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 


  reply	other threads:[~2009-05-20  5:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30  7:42 EXT vs XFS at 80% filled filesystem Milind Dumbare
2009-04-30 18:34 ` Theodore Tso
2009-05-18 13:03   ` Milind
2009-05-18 13:17     ` Theodore Tso
2009-05-20  5:43       ` Milind [this message]
2009-05-20 10:50         ` Theodore Tso
2009-05-20 11:51           ` Milind
2009-05-20 14:20             ` Theodore Tso
2009-05-20 12:46           ` Matthew Wilcox

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=1242798210.3457.4.camel@alhena \
    --to=milind@gslab.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --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 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).