Re: creation of a directory

Noel Yap wrote: > It's even uglier when you're dealing with macros: > > $(FOO): $(dir $(FOO)). Correction, this should be: $(FOO): | $(dir $(FOO)). Noel -- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibite

RE: filter-out, very slow?

Thanks for your help Ted, I really liked the MAKE_LONG_LIST, I'm sure I will find a use for such a function in the future. However, I does not look too hard to code filter-out in such a way that it is 100 times faster. I looks n^2 now, and by using more memory (hash) it could become 1-1.5*O(n) qui

Re: creation of a directory

Boris Kolpackov wrote: > > Hi Noel, > > > Since there is a workaround, simplifying GNU make in this respect > > isn't worth it. > > Speaking of workaround, having the following implicit rule > > %/. : > @mkdir $* > > you cannot just write > > foo : bar/ > > instead you will have to w

Re: filter-out, very slow?

On 30 Jan 2004 at 11:03 PST, Ted Stern wrote: > > On 30 Jan 2004 at 09:55 PST, Daniel Shane wrote: >> I see, >> >> In that case, could we add a new text function that would work like >> filter-out, but simply faster? We could call it comm. The reason is quite >> simple, when strings become overwhel

Re: filter-out, very slow?

On 30 Jan 2004 at 09:55 PST, Daniel Shane wrote: > I see, > > In that case, could we add a new text function that would work like > filter-out, but simply faster? We could call it comm. The reason is quite > simple, when strings become overwhelming, it is impossible to pass them to a > shell script

Re: creation of a directory

Hi Paul, > It's done so that if you write: > > foo: bar/ > > in one place in your makefile, and: > > bar: biz > > another place, and: > > boz: $(CURDIR)/bar > > in a third place, make realizes they are all the same target and won't > try to build them multiple times (or, say "do

Re: filter-out, very slow?

On Fri, Jan 30, 2004 at 12:34:50PM -0500, Daniel Shane wrote: > For users, that means that instead of > > $(filter-out $(str1), $(str2)) > > it woudl become > > $(filter-out ($sort $(str1)), ($sort $(str2))) That would in some usages have influence on linking order, which will be a disaster to

Re: creation of a directory

"Paul D. Smith" wrote: > It's done so that if you write: > > foo: bar/ > > in one place in your makefile, and: > > bar: biz > > another place, and: > > boz: $(CURDIR)/bar > > in a third place, make realizes they are all the same target and won't > try to build them multiple times

Re: creation of a directory

%% Boris Kolpackov <[EMAIL PROTECTED]> writes: bk> Hi Paul, >> GNU make strips trailing slashes, so that "foo/" and "foo" are >> considered the same prerequisite. bk> Is it because make just does it this way or there is some deep bk> reason for that? It's done so that if you write:

RE: filter-out, very slow?

I see, In that case, could we add a new text function that would work like filter-out, but simply faster? We could call it comm. The reason is quite simple, when strings become overwhelming, it is impossible to pass them to a shell script because of command line size limit. Therefore, they are not

Re: filter-out, very slow?

%% "Daniel Shane" <[EMAIL PROTECTED]> writes: ds> I'm using the filter out function on some very big strings and ds> found out that the filter-out is much slower than comm (shell ds> command). Would it be hard to change the filter-out function so ds> that it accepts already sorted inputs?

filter-out, very slow?

Hi, I'm using the filter out function on some very big strings and found out that the filter-out is much slower than comm (shell command). Would it be hard to change the filter-out function so that it accepts already sorted inputs? That would make the algorithm much faster, as it looks like O(n^n)

Re: creation of a directory

Hi Paul, > GNU make strips trailing slashes, so that "foo/" and "foo" are > considered the same prerequisite. Is it because make just does it this way or there is some deep reason for that? For example, $(dir) does not strip the trailing slash. Oh, but $(@D) does... > You can get your makefile

Re: creation of a directory

"Paul D. Smith" wrote: > GNU make strips trailing slashes, so that "foo/" and "foo" are > considered the same prerequisite. Is there any reason, other than backwards compatibility, to keep this particular feature? I find it a bit annoying although the workaround is feasible. Thanks, Noel -- NO

Re: creation of a directory

%% Boris Kolpackov <[EMAIL PROTECTED]> writes: bk> I was wondering if there is a valid reason for the following makefile bk> not to work. bk> hello : | foo/ bk> hello : bk> @echo hello bk> %/ : bk> mkdir $* GNU make strips trailing slashes, so that "foo/" and "foo" are consid

Any help needed?

Hello. Recently I've decided to spend some time on open-source project - and after short search I've found (on savannah site) list of projects that need help - 'make' was among them. That site (http://savannah.gnu.org/people/viewjob.php?group_id=3972&job_id=200) claimed that some improvements for

Build problem on LynxOS

Hi I just tried to build make 3.80 on LynxOS 3.0.1 and noticed that file main.c does not compile. I added #include to main.c to fix this. Is it possible to add this fix to the next make release? Regards, Olli ___ Bug-make mailing list [EMAIL PROTECTE

creation of a directory

Good day, I was wondering if there is a valid reason for the following makefile not to work. hello : | foo/ hello : @echo hello %/ : mkdir $* thanks, -boris signature.asc Description: Digital signature ___ Bug-make mailing list [EMA