public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kfir Lavi <lavi.kfir@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] configure: error: C++ compiler cannot create executables
Date: Fri, 31 Dec 2010 19:07:44 +0200	[thread overview]
Message-ID: <AANLkTi=5xzKj-nN55BFOnFBBFpMFUm0JJ4Op7=gsHMnK@mail.gmail.com> (raw)
In-Reply-To: <20101231011509.GA2178@nibiru.local>

[-- Attachment #1: Type: text/plain, Size: 2487 bytes --]

On Fri, Dec 31, 2010 at 3:15 AM, Enrico Weigelt <weigelt@metux.de> wrote:

> * Kfir Lavi <lavi.kfir@gmail.com> schrieb:
>
> > > Patching autogenerated files is not a good idea - change the
> > > actual source and regenerate.
> > >
> > In the ACE files they ask not to generate configure alone.
>
> Well, not the first time I hear upstreams confusing intermediate
> files w/ actual sources (yes, there're also folks who include
> precompiled binaries, which are run and later recompiled within
> the build process ;-o). A very good indicator for something
> completely conceptionally wrong in here ;-p
>
> My approach (which I'm doing in the OSS-QM project) is radically
> clear: autogenerated files *must* be regenerated on each build.
> If this doesn't work, the source is broken and has to be fixed,
> period ;-p
>
> Well, you are a purist ;-)
The thing is, I must use this ACE libs, and they are broken.
I have also so many other things to get working, I just have to live with
this approach.
Your method regenerating the ./configure script, is very good, and I'm
asking myself, why
its not done every install, or why we get ./configure generated in the
tar.gz.
Maybe there is something to it.


> I'm even going farer: if upstream has an proper vcs, I take the
> releases from there, completely regenerating everything from
> scratch. All fixes are done within my VCS (essentially, I always
> have my own releases ontop the upstream's, as git tags). Sometimes
> you encounter packages, eg. coreutils, which doing really messy
> things like pulling in another tree via git and copying in files
> from there - a nightmare for packagers ;-o
>
> I wonder, do you patch every ebuild to do just that?
Maybe there should be a new FEATURE that request the ebuild to download the
release from the VCS.

 > So I tried it ;)
> > But had problem to finish.
> > My guess they still tweak by hand.
>
> WTF ? Tweak autoconf-generated files by hand ? Oh, I don't even
> wanna know which drugs they're on ;-)
>
>

> cu
> --
> ----------------------------------------------------------------------
>  Enrico Weigelt, metux IT service -- http://www.metux.de/
>
>  phone:  +49 36207 519931  email: weigelt@metux.de
>  mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
> ----------------------------------------------------------------------
>  Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
> ----------------------------------------------------------------------
>
>

[-- Attachment #2: Type: text/html, Size: 3768 bytes --]

  reply	other threads:[~2010-12-31 18:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31  8:08 [gentoo-embedded] configure: error: C++ compiler cannot create executables Kfir Lavi
2010-11-02 12:49 ` Manuel Lauss
2010-11-03 10:33   ` Kfir Lavi
2010-11-03 17:50     ` Kfir Lavi
2010-11-03 18:32       ` Kfir Lavi
2010-11-08 10:04         ` Kfir Lavi
2010-12-05 19:52           ` Enrico Weigelt
2010-12-23 16:43           ` Kfir Lavi
2010-12-30  6:27             ` Enrico Weigelt
2010-12-30 12:21               ` Kfir Lavi
2010-12-31  1:15                 ` Enrico Weigelt
2010-12-31 17:07                   ` Kfir Lavi [this message]
2011-01-02 22:38                     ` Enrico Weigelt
2011-01-03 15:00                       ` Peter Stuge
2011-02-05 15:16                         ` Enrico Weigelt
2011-02-06  7:21                           ` Mike Frysinger
2011-02-13 22:28                             ` Enrico Weigelt
2011-02-14  5:30                               ` Mike Frysinger

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='AANLkTi=5xzKj-nN55BFOnFBBFpMFUm0JJ4Op7=gsHMnK@mail.gmail.com' \
    --to=lavi.kfir@gmail.com \
    --cc=gentoo-embedded@lists.gentoo.org \
    /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