On 09/05/2012 09:15 PM, Warren Block wrote:
On Wed, 5 Sep 2012, Tim Daneliuk wrote:
On 09/05/2012 07:24 PM, Bryan Drewery wrote:
On 9/5/2012 7:02 PM, Tim Daneliuk wrote:
A bit off topic, but I'm kind of stuck. I am using gmake and want to
do something like this:
FOO := $(shell a | b | c
On Wed, 5 Sep 2012, Tim Daneliuk wrote:
On 09/05/2012 07:24 PM, Bryan Drewery wrote:
On 9/5/2012 7:02 PM, Tim Daneliuk wrote:
A bit off topic, but I'm kind of stuck. I am using gmake and want to
do something like this:
FOO := $(shell a | b | c)
But this appears not to work. Only the 'a
On 09/05/2012 07:24 PM, Bryan Drewery wrote:
On 9/5/2012 7:02 PM, Tim Daneliuk wrote:
A bit off topic, but I'm kind of stuck. I am using gmake and want to
do something like this:
FOO := $(shell a | b | c)
But this appears not to work. Only the 'a' command is executed. The
remainder
of t
On 9/5/2012 7:02 PM, Tim Daneliuk wrote:
> A bit off topic, but I'm kind of stuck. I am using gmake and want to
> do something like this:
>
>FOO := $(shell a | b | c)
>
> But this appears not to work. Only the 'a' command is executed. The
> remainder
> of the pipeline is ignored. Is there
A bit off topic, but I'm kind of stuck. I am using gmake and want to
do something like this:
FOO := $(shell a | b | c)
But this appears not to work. Only the 'a' command is executed. The remainder
of the pipeline is ignored. Is there some clean way to implement this
kind of thing?
--
--
On Wed, Mar 02, 2011 at 01:27:22PM +, b. f. wrote:
> > In particular I was surprised
> > to find out that GNU make considers
> > suffix rules obsolete:
> > http://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html#Suffix-Rules
> >
> > I didn'
> In particular I was surprised
> to find out that GNU make considers
> suffix rules obsolete:
> http://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html#Suffix-Rules
>
> I didn't think the suffix rules are
> obsolete in BSD make, are they?
>
No (Although
I just discovered that my FreeBSD Makefile
fails miserably on a linux system with
GNU Make 3.80.
In particular I was surprised
to find out that GNU make considers
suffix rules obsolete:
http://www.gnu.org/software/make/manual/html_node/Suffix-Rules.html#Suffix-Rules
I didn't think the s
On Fri, 11 Feb 2011 10:26:13 +0200, Vikash Badal wrote:
> Make all produces the follow output:
>
> make all
> cc -o bin/nntpd -lpthread -lmysqlclient_r -Wall -g -Iinclude
> -I/usr/local/include -I/usr/local/include/mysql -L/usr/local/lib
> -L/usr/local/lib/mysql obj/log.o obj/cleanup.o obj/config.
On Thu, 10 Feb 2011 17:59:14 -0600 (CST), Robert Bonomi
wrote:
>> From: Vikash Badal
>> Date: Thu, 10 Feb 2011 11:30:02 +0200
>> Subject: RE: switching from gnu make to bsd make
>>
>> > -Original Message-
>> > From: Polytropon [mailto:free
> -Original Message-
> From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
> questi...@freebsd.org] On Behalf Of Robert Bonomi
> Sent: 11 February 2011 01:59 AM
> To: Vikash Badal
> Cc: freebsd-questions@freebsd.org
> Subject: Re: switching from gnu make
> From: Vikash Badal
> Date: Thu, 10 Feb 2011 11:30:02 +0200
> Subject: RE: switching from gnu make to bsd make
>
> > -Original Message-
> > From: Polytropon [mailto:free...@edvax.de] Sent: 10 February 2011 10:11
> > AM To: Vikash Badal Cc: freebsd-que
On Thu, Feb 10, 2011 at 8:32 AM, Vikash Badal wrote:
> Can someone please advise me as to how I switch the following lines of gnu
> make to bsd make
>
>
> $(OBJDIR)/%.o:${SRCDIR}/%.c
> ${CC} -c ${CFLAGS} ${INCDIR} ${LIBDIR} $< -o $@
>
I use BSD make for XML and XS
> -Original Message-
> From: Polytropon [mailto:free...@edvax.de]
> Sent: 10 February 2011 10:11 AM
> To: Vikash Badal
> Cc: freebsd-questions@freebsd.org
> Subject: Re: switching from gnu make to bsd make
>
> Of course, in my testing case OBJDIR and SRCDIR a
On Thu, 10 Feb 2011 09:32:06 +0200, Vikash Badal wrote:
> Can someone please advise me as to how I switch the following lines of gnu
> make to bsd make
>
>
> $(OBJDIR)/%.o:${SRCDIR}/%.c
> ${CC} -c ${CFLAGS} ${INCDIR} ${LIBDIR} $< -o $@
It sems to work with BS
Can someone please advise me as to how I switch the following lines of gnu make
to bsd make
$(OBJDIR)/%.o:${SRCDIR}/%.c
${CC} -c ${CFLAGS} ${INCDIR} ${LIBDIR} $< -o $@
Thanks
Vikash
Please note: This email and its content are subject to the disclaimer as
displayed at the follow
On Tuesday 17 April 2007 13:15:08 Bill Campbell wrote:
> The gmake program has many extensions which tend to be used in
> the gnu automake, autoconf, libtools system.
>
> I suspect that gmake will work with most non-gnu Makefiles, but
> the reverse is not true.
This suspicion is not necessarily tr
On Tue, 2007-04-17 at 17:28 +0100, Soo-Hyun Choi wrote:
> Hi,
>
> This might be a dumb question, but would like get a clear idea about
> the differences between BSD make and GNU make. Why do I have to do
> 'gmake' in some cases instead of just plain 'make
>/usr/bin/local/bin/convert $1.gif $1.jpg
>
> but this obviously doesn't work (I didn't really expect it to). Neither does
>
> for $i (*.jpg) {
> $i.jpg: $i.gif
> /usr/bin/local/bin/convert $i.gif $i.jpg
> }
Following worked with both BSD &am
Here's a Makefile that converts 3 GIFs to JPGs in a given directory:
1.jpg: 1.gif
/usr/local/bin/convert 1.gif 1.jpg
2.jpg: 2.gif
/usr/local/bin/convert 2.gif 2.jpg
3.jpg: 3.gif
/usr/local/bin/convert 3.gif 3.jpg
How do I generalize this to apply to ALL the GIFs in a given
dire
On Tue, Apr 17, 2007, Soo-Hyun Choi wrote:
>Hi,
>
>This might be a dumb question, but would like get a clear idea about
>the differences between BSD make and GNU make. Why do I have to do
>'gmake' in some cases instead of just plain 'make'?
>
>What'
On Apr 17, 2007, at 9:28 AM, Soo-Hyun Choi wrote:
This might be a dumb question, but would like get a clear idea about
the differences between BSD make and GNU make. Why do I have to do
'gmake' in some cases instead of just plain 'make'?
Because people write more complex ma
Hi,
This might be a dumb question, but would like get a clear idea about
the differences between BSD make and GNU make. Why do I have to do
'gmake' in some cases instead of just plain 'make'?
What's the differences?
Thanks,
In the last episode (Jul 13), David Kelly said:
> On Wed, Jul 13, 2005 at 02:08:07PM -0500, Dan Nelson wrote:
> > I believe "-include .depend" will tell gmake to try to include the
> > file but not complain if it's not there.
>
> Yes! That does work!
>
> OTOH it breaks in BSD Make. :-(
Automake
On Wed, Jul 13, 2005 at 02:08:07PM -0500, Dan Nelson wrote:
>
> I believe "-include .depend" will tell gmake to try to include the file
> but not complain if it's not there.
Yes! That does work!
OTOH it breaks in BSD Make. :-(
Thought to try something like this which makes BSD happy but breaks
In the last episode (Jul 13), David Kelly said:
> Yes, but the problem is that I want to make GNU Make behave the BSD way.
> Specifically my application is an embedded AVR and it really needs to
> build fairly painlessly under the WinAVR environment where GNU Make is
> painlessly bu
On Wed, Jul 13, 2005 at 05:12:57PM +0100, Alex Zbyslaw wrote:
> David Kelly wrote:
>
> >So my question is "Is there a way to make GNU Make handle .depend the
> >BSD way? And is it possible for the same Makefile to run the same way on
> >either BSD or GNU Makes?"
David Kelly wrote:
So my question is "Is there a way to make GNU Make handle .depend the
BSD way? And is it possible for the same Makefile to run the same way on
either BSD or GNU Makes?"
I don't know the answer to your question (but I suspect it's "no, un
BSD make will automatically and silently include .depend if one exists
in the same directory as the Makefile. Otherwise it won't complain if
.depend is missing.
In GNU Make one must explicitly "include .depend", but if .depend does
not exist GNU Make aborts. And can't
n't find .depend if the
filename is still quoted.
This works in BSD make altho its not doing anything that isn't
automatically done:
.include ".depend"
Above is apparently the same as this in GNU make and accepted by BSD:
include .depend
This does not work in BSD as it seems to b
uses .depend if one is found. GNU make
> requires the file be named in an include, but the syntax of GNU
> include is different than BSD. As is the syntax of conditional
> statements.
FreeBSD's make understands the gnu-style include syntax with no leading
dot, even though it's und
I got the silly idea that I want one Makefile to work with both BSD and
GNU makes. Silly me. Fairly simple Makefiles work but when expanding my
Makefile to include .depend generation I get tripped.
BSD make automagically uses .depend if one is found. GNU make requires
the file be named in an
On 2004-12-28 09:53, Len Zettel <[EMAIL PROTECTED]> wrote:
> Are there any serious differences between GNU make and the FreeBSD
> make command?
Yes. These two programs serve a similar purpose and you may carefully
write Makefiles that use a very minimal feature set of both that ha
Len Zettel <[EMAIL PROTECTED]> writes:
> Are there any serious differences between
> GNU make and the FreeBSD make command?
Yes.
> Will the information in the GNU make
> manual be relevant?
Only if you're using GNU make.
__
Are there any serious differences between
GNU make and the FreeBSD make command?
Will the information in the GNU make
manual be relevant?
-LenZ-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Is there a good doc out there explaining the differences?
I cannot seem to find anything with either google or teoma.
jm
--
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
Hi,
On Fri, Feb 20, 2004 at 11:02:43AM +0300, Igor B. Bykhalo wrote:
> How can this GNU make constuct converted to FreeBSD:
>
> > SRCDIRS = convert/c misc/c string/c memory/c handleio/c startup/c environ/c
> >
> > vpath %.c $(SRCDIRS)
> ?
>
> Is there some gui
How can this GNU make constuct converted to FreeBSD:
> SRCDIRS = convert/c misc/c string/c memory/c handleio/c startup/c environ/c
>
> vpath %.c $(SRCDIRS)
?
Is there some guide on the topic? I am new to this...
TIA,
Igor
___
[EMAIL
38 matches
Mail list logo