From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problems rebuilding the DENX ELDK
Date: Thu, 24 Jul 2003 10:18:05 +0200 [thread overview]
Message-ID: <3F1F963D.4010609@imc-berlin.de> (raw)
In-Reply-To: <20030724075838.5964DC6D82@atlas.denx.de>
Dear Wolfgang,
> Dear Steven,
>
> in message <3F1F8738.3040209@imc-berlin.de> you wrote:
>
>>I am trying to rebuild the great DENX's ELDK from scratch.
>>My host is a SuSE 8.2 system.
>>The first obstacle is that some packages won't build with recent
>>automake/autoconf version. So I got some old versions built and
>>installed them on my system.
>>
>>Now the first step - build the RPM - works. I do get a rpm binary in
>>/opt/eldk/build/ppc-2003-07-23/work/bin
>
>
> Just a note: if this is not really urgent, you might just want to
> wait a bit. We're working on the next release of the ELDK, which will
> be based on YD-3.0, which contains rpm-4.1
>
> I guess we will have to validate this release with a SuSE system,
> too.
Jippieh!!!
I test! I test! :o)
I made it once to rebuild the ELDK under a modified SuSE 8.0. But I
can't do it again. I just can't remember what I did. But as long as I
am not able to rebuild it I can't update my build host to a more
recent SuSE version... :-(
So I think I can wait (how long?). But any idea about my original
question?
I'd love to understand this whole automake/autoconf/rpm stuff?
I suppose the times of handwriten/optimized Makefiles are gone...
Forever... ;-)
Thanks,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-24 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 7:14 Problems rebuilding the DENX ELDK Steven Scholz
2003-07-24 7:58 ` Wolfgang Denk
2003-07-24 8:18 ` Steven Scholz [this message]
2003-07-24 10:47 ` Wolfgang Denk
2003-07-24 14:25 ` Steven Scholz
-- strict thread matches above, loose matches on Subject: below --
2003-07-24 12:34 Wells, Charles
2003-07-24 12:45 Holger L. Bille
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=3F1F963D.4010609@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.