Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/xerces
Date: Wed, 21 Jan 2009 08:31:14 +0100	[thread overview]
Message-ID: <1232523074.11888.2.camel@elrond.atmel.com> (raw)
In-Reply-To: <87y6x5vc74.fsf@macbook.be.48ers.dk>

tis 2009-01-20 klockan 23:34 +0100 skrev Peter Korsgaard:
> >>>>> "ulf" == ulf  <ulf@uclibc.org> writes:
> 
>  ulf> Author: ulf
>  ulf> Date: 2009-01-20 21:34:46 +0000 (Tue, 20 Jan 2009)
>  ulf> New Revision: 24928
> 
>  ulf> Log:
>  ulf> Bump xerces-c to latest stable, ARM build now completes
> 
>  ulf> Modified:
>  ulf>    trunk/buildroot/package/xerces/Config.in
>  ulf>    trunk/buildroot/package/xerces/xerces.mk
> 
> How about converting to Makefile.autotools.in format while you're at
> it?

I think my priority is to get things to build at all.

Once all packages build, then it will not be hard
to get most of them into Makefile.autotools.in 

BTW: Makefile.autotools.in does not support compressed
patches *.patch.gz, *.patch.bz2, is that intentional?

BR
Ulf Samuelsson

>  ulf> +xerces-unpacked: $(XERCES_DIR)/.unpacked
>  ulf> +
>  ulf>  xerces-clean:
>  ulf>  	rm -rf $(STAGING_DIR)/usr/include/xercesc
>  ulf>  	rm -f $(STAGING_DIR)/lib/libxerces*
> 
> TARGET_DIR cleanup stuff seems to be missing.
> 

OK, Have a look at it later.
BR
Ulf Samuelsson

  reply	other threads:[~2009-01-21  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 21:34 [Buildroot] svn commit: trunk/buildroot/package/xerces ulf at uclibc.org
2009-01-20 22:34 ` Peter Korsgaard
2009-01-21  7:31   ` Ulf Samuelsson [this message]
2009-01-21 12:25     ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2009-01-16 13:27 jacmet at uclibc.org

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=1232523074.11888.2.camel@elrond.atmel.com \
    --to=ulf.samuelsson@atmel.com \
    --cc=buildroot@busybox.net \
    /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