Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Autotools and "foreign"
Date: Wed, 13 Aug 2014 07:13:47 +0200	[thread overview]
Message-ID: <53EAF40B.8050301@topic.nl> (raw)
In-Reply-To: <CAJTo0LY+Kp14Sn4bdFtX4eYCK4Oea52MEG-=s6TbG_CKoMx9Pg@mail.gmail.com>

On 08/12/2014 08:57 PM, Burton, Ross wrote:
> On 12 August 2014 18:40, Mike Looijmans <mike.looijmans@topic.nl> wrote:
>> Is there an alternative to manually patching all of these packages to get
>> them to compile once more?
>
> Depends on the package, but generally you'll need to update the
> automake macro at the top of configure.ac (and submit a patch upstream
> as this should have been fixed years ago).

Basically, you're saying "no" then?

> Encouraging said upstreams to use autoreconf instead of (likely)
> home-grown crazy would be a good move whilst you're talking to them.

That might be the case if said upstream people actually still existed. Most of 
these packages have since long been abandoned.

So I guess I'll have to cook up a class that works around it, just adding the 
"missing" files into the S directory might do the trick.

Mike.


Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Bezoek ons op 9 en 10 september tijdens Technology for Health Den Bosch (stand 53)
http://www.technologyforhealth.nl



  reply	other threads:[~2014-08-13  5:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 17:40 Autotools and "foreign" Mike Looijmans
2014-08-12 18:57 ` Burton, Ross
2014-08-13  5:13   ` Mike Looijmans [this message]
2014-08-13  5:35     ` Robert Yang
2014-08-13  9:29     ` Burton, Ross

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=53EAF40B.8050301@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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