-±×¸²ÀÌ ¾Èº¸À̸é [À̹ÌÁöº¸±â]-¸¦ Ŭ¸¯ ÇØ ÁÖ¼¼¿ä -
¹Ù·Î°¡±â
Find local movie times and trailers on Yahoo! Movies.
Greetings,
Our company expands its high-tech retail markets to new countries. Because of physical
remoteness we have opened some new vacancies for making simple and easy work. No
experience or special skills are required for it. Your willingness and honesty are
just enough. Our company i
Albert Chin wrote:
> On Fri, Sep 17, 2004 at 02:49:05PM +0100, Gary V. Vaughan wrote:
>
>>It may be small consolation, but the next release of GNU m4 has the last
>>bit of functionality required to eliminate aclocal entirely.
>
> How does it do that? If the .m4 files for libtool 1.4 are in
> /op
On Fri, Sep 17, 2004 at 02:49:05PM +0100, Gary V. Vaughan wrote:
> It may be small consolation, but the next release of GNU m4 has the last
> bit of functionality required to eliminate aclocal entirely.
How does it do that? If the .m4 files for libtool 1.4 are in
/opt/libtool14 and the .m4 files f
Hi Albert,
Albert Chin wrote:
> On Fri, Sep 17, 2004 at 10:50:09AM +0200, Andreas Schwab wrote:
>
>>Albert Chin <[EMAIL PROTECTED]> writes:
>>
>>
>>>When building software with installable .m4 files (libtool, pkgconfig,
>>>gtk+, etc.), if each software program is installed to a separate
>>>direct
On Fri, Sep 17, 2004 at 10:50:09AM +0200, Andreas Schwab wrote:
> Albert Chin <[EMAIL PROTECTED]> writes:
>
> > When building software with installable .m4 files (libtool, pkgconfig,
> > gtk+, etc.), if each software program is installed to a separate
> > directory, aclocal must be used like so:
>
Albert Chin <[EMAIL PROTECTED]> writes:
> When building software with installable .m4 files (libtool, pkgconfig,
> gtk+, etc.), if each software program is installed to a separate
> directory, aclocal must be used like so:
> $ aclocal -I [path to libtool .m4 files] \
> -I [path to pkgconfig .m
