From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix host tool build breakage, take two
Date: Tue, 01 Apr 2008 22:41:26 +0200 [thread overview]
Message-ID: <20080401204126.31CD724544@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 01 Apr 2008 10:04:00 CDT." <5D708345-1CF3-46FA-B9D2-689C52625177@kernel.crashing.org>
In message <5D708345-1CF3-46FA-B9D2-689C52625177@kernel.crashing.org> you wrote:
>
> > I don't know RHEL - maybe you can update the RPM?
>
> Not that I'm aware of. Its a box run by our IT department so I have
> no ability to upgrade or modify things. It looks like RHEL4 has the
> same issue.
>
> ld2047$ rpm -qf /usr/include/md5.h
> cyrus-sasl-devel-2.1.19-5.EL4
I see. I have to go back pretty far in time to find such a
configuration:
$ ls -l /usr/include/md5.h
-rw-r--r-- 1 root root 1572 Apr 24 2006 /usr/include/md5.h
$ rpm -qf /usr/include/md5.h
cyrus-sasl-devel-2.1.20-6
$ cat /etc/issue
Fedora Core release 4 (Stentz)
All more recent distros seem to have this fixed (and yes,
cyrus-sasl-devel is installed in all of them):
$ ls -l /usr/include/md5.h
ls: /usr/include/md5.h: No such file or directory
$ cat /etc/issue
Fedora Core release 5 (Bordeaux)
$ ls -l /usr/include/md5.h
ls: /usr/include/md5.h: No such file or directory
$ cat /etc/issue
Fedora Core release 6 (Zod)
$ ls -l /usr/include/md5.h
ls: cannot access /usr/include/md5.h: No such file or directory
$ cat /etc/issue
Fedora release 7 (Moonshine)
$ ls -l /usr/include/md5.h
ls: cannot access /usr/include/md5.h: No such file or directory
$ cat /etc/issue
Fedora release 8 (Werewolf)
> Any ideas on how to work around this? Do we really intend to pick up
> the system md5.h or should we be getting the one from u-boot/include/
> md5.h?
We need the system md5.h, I think. We'll investigate.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Why should we subsidize intellectual curiosity?" - Ronald Reagan
next prev parent reply other threads:[~2008-04-01 20:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 14:06 [U-Boot-Users] [PATCH] Fix host tool build breakage, take two Bartlomiej Sieka
2008-03-27 14:44 ` Markus Klotzbücher
2008-03-27 14:44 ` Haavard Skinnemoen
2008-03-28 13:19 ` Kumar Gala
2008-03-28 14:45 ` Wolfgang Denk
2008-03-28 15:44 ` Kumar Gala
2008-03-31 16:50 ` Kumar Gala
2008-03-31 20:23 ` Wolfgang Denk
2008-04-01 15:04 ` Kumar Gala
2008-04-01 20:41 ` Wolfgang Denk [this message]
2008-04-02 14:55 ` Kumar Gala
2008-04-02 15:59 ` Bartlomiej Sieka
2008-04-02 17:24 ` Kumar Gala
2008-04-02 18:57 ` Wolfgang Denk
2008-04-02 21:19 ` [U-Boot-Users] [RFC] Rename include/md5.h to u-boot-md5.h Andy Fleming
2008-04-02 21:50 ` Kumar Gala
2008-04-02 22:06 ` Andy Fleming
2008-04-03 21:49 ` Timur Tabi
2008-04-06 11:18 ` Jean-Christophe PLAGNIOL-VILLARD
2008-04-14 1:09 ` Wolfgang Denk
2008-04-03 16:33 ` [U-Boot-Users] [PATCH] Fix host tool build breakage, take two Bartlomiej Sieka
2008-04-03 18:26 ` Wolfgang Denk
2008-04-03 18:36 ` Scott Wood
2008-04-03 20:09 ` Andy Fleming
2008-04-03 22:04 ` Wolfgang Denk
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=20080401204126.31CD724544@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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