Re: [owl-users] crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems

• Previous message: Vincent Danen: "[owl-users] crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems"
• In reply to: Vincent Danen: "[owl-users] crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems"
• Next in thread: Vincent Danen: "Re: [owl-users] crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems"
• Reply: Vincent Danen: "Re: [owl-users] crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi,
On Fri, May 19, 2006 at 11:08:38PM -0600, Vincent Danen wrote:
[...]
> crypt-entry.c:74: warning: function declaration isn't a prototype
> crypt-entry.c:142: error: 'fcrypt' aliased to undefined symbol 'crypt'
[...]
> Any ideas on what might be causing the problem?

Modern gcc requires to make symbol definition available for weak_alias.

In unpatched glibc, "crypt" symbol is defined in the same file
(crypt-entry.c) as "fcrypt" alias.
In crypt_blowfish (up to 1.0.1), the "crypt" symbol is defined in wrapper.c
as weak alias to "__crypt".  Obvious fix would be to move "fcrypt"
definition from crypt-entry.c to wrapper.c


-- 
ldv

• application/pgp-signature attachment: stored

• Previous message: Vincent Danen: "[owl-users] crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems"
• In reply to: Vincent Danen: "[owl-users] crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems"
• Next in thread: Vincent Danen: "Re: [owl-users] crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems"
• Reply: Vincent Danen: "Re: [owl-users] crypt_blowfish 1.0.1, glibc 2.3.5, and gcc 4.0.3 compile problems"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.3 : Sat May 20 2006 - 05:53:58 PDT