[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Faure..

On Sat, May 29, 1999 at 05:34:02PM -0600, Jason Gunthorpe wrote:
> I finished upgrading faure to glibc2.1 and alas all sorts of things are
> broken now. slapd won't start, exim gives errors like:

  openldap runs on my system without noticable problems... But then again, I
  don't use it that much. If you want to try my packages

| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name            Version        Description
ii  openldap-gatewa 2.0.0-4        OpenLDAP Gateways
ii  openldap-utils  2.0.0-4        OpenLDAP utilities.
ii  openldapd       2.0.0-4        OpenLDAP server (slapd).

> faure{root}/tmp#runq -qf
> 1999-05-29 18:31:18 10ns3U-00085B-00 regular expression error:
> unrecognized character after (? at offset 7 while compiling
> (?i)^(?>(?(1)\.|())[^\W_](?>[a-z0-9-]*[^\W_])?)+
> The exim pcre library will not compile with errors like,
> faure{jgg}/tmp/pcre-1.09#make
> gcc -shared -Wl,-soname,libpcreposix.so.1 -o libpcreposix.so.1 -lc -L.
> -lpcre pcreposix.o-pic
> /usr/bin/ld: libpcreposix.so.1: undefined versioned symbol name
> regexec@@GLIBC_2.0
> /usr/bin/ld: failed to set dynamic section sizes: Bad value
> collect2: ld returned 1 exit status
> make: *** [libpcreposix.so.1] Error 1

Instal libpcre2 instead. It builds without problems on my machine (it has
LOADS of warnings though...)

chown -R root.root debian/tmp
chmod -R g-ws debian/tmp
dpkg --build debian/tmp ..
dpkg-deb: building package `exim' in `../exim_2.11-4_alpha.deb'.
# Build eximon package


chown -R root.root debian/tmp
chmod -R go=rX debian/tmp
dpkg --build debian/tmp ..
dpkg-deb: building package `eximon' in `../eximon_2.11-4_alpha.deb'.
 dpkg-genchanges -B -mbartw@debian.org


On faure:
$ dpkg -S libpcreposix.so.1 
libpcre1: /usr/lib/libpcreposix.so.1.09
libpcre1: /usr/lib/libpcreposix.so.1

> Bash is also giving SIGILL errors in some conditions.. 

  Do you have some debugging leads like coredumps or a command that surely
  leads to these errors? I personally do not use bash (as main shell) so some
  pointers are welcomed.

B. Warmerdam                                              GNU/Debian Linux
bartw@xs4all.nl, bartw@debian.org (Keyid: 10A0FDD1)       ----------------

Reply to: