Hi Simon,
problem is, that the build machine (SLES9, glibc 2.3.3)
is newer than RHEL3 (glibc 2.3.2).
It's recommended to use MaxDB 7.6 with RHEL4.
The combination MaxDB 7.5 and RHEL3 works fine.

Regards,
 Daniel
 

-----Original Message-----
From: Simon Matter [mailto:[EMAIL PROTECTED] 
Sent: Freitag, 28. Juli 2006 10:38
To: Schmoger, Daniel
Cc: maxdb@lists.mysql.com
Subject: RE: maxdb 7.6.0.32 rpms depend on glibc 2.3.4

> Hello Simon,
> our linux build machines run with SuSE Linux Enterprise 9.
> This Linux uses a glibc 2.3.3, which provides a symbol GLIBC_2.3.4.
> In MaxDB 7.6.00.27 this version symbol wasn't linked, but in version
> 7.6.00.32 it was.
> At the moment i'm not knowing why, but we will investigate. Maybe a
new
> libc feature was used or ldflags were modified.

Hi Daniel,

Is there any news about the glibc requirements? Unfortunately building
MaxDB is still not an easy task that's why I'm still using the packages
provided, which now are not usable on RHEL3 anymore.

Thanks,
Simon

>
> Best regards,
>  Daniel
>
>
> -----Original Message-----
> From: Simon Matter [mailto:[EMAIL PROTECTED]
> Sent: Donnerstag, 20. Juli 2006 11:14
> To: maxdb@lists.mysql.com
> Subject: maxdb 7.6.0.32 rpms depend on glibc 2.3.4
>
> Hi,
>
> The latest maxdb rpms 7.6.0.32 depend on glibc-2.3.4, which makes them
> unusable on distributions like RedHat EL3, which uses glibc-2.3.2. Is
> there a reason why this specific glibc version is needed now?
>
> Thanks,
> Simon
>
> --
> MaxDB Discussion Mailing List
> For list archives: http://lists.mysql.com/maxdb
> To unsubscribe:
> http://lists.mysql.com/[EMAIL PROTECTED]
>

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to