| To: | John Trostel <jtrostel@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: libacl.lai vs. libacl.la in cmd/acl |
| From: | Dean Roehrich <roehrich@xxxxxxx> |
| Date: | Mon, 13 Aug 2001 16:35:35 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
>From: John Trostel <jtrostel@xxxxxxxxxxxxxx> >Soooo.... when is it supposed to get installed? By the time I have finished ou >t >of the ../cmd/acl make configure, make, make install I would think it _should_ >be installed. If I am making no other utilities it would _need_ to be installe >d >by then. It's installed during make install_dev. If you aren't installing the dev package then I'm not sure why you'd need the libacl.la. Let's not let the tail wag the dog here--that libtool warning is nothing more than an annoyance (in a long list of libtool annoyances). Or am I missing something that you're asking about? Dean |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: problem compiling dmapi, Derek Glidden |
|---|---|
| Next by Date: | TAKE - add <sys/types.h> to dmapi.h for slackware, Dean Roehrich |
| Previous by Thread: | Re: libacl.lai vs. libacl.la in cmd/acl, John Trostel |
| Next by Thread: | TAKE - add <sys/types.h> to dmapi.h for slackware, Dean Roehrich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |