search for: woulf

Hi, FLAC helpfully provides a flac.pc file. Unfortunately there is a nasty interaction between that file and system header files. If ones installs flac and relies on pkg-config to find the CFLAGS one woulf get CFLAGS value of "-I${includedir}/FLAC" which suggests that FLAC header files like <metadata.h> should be included as: #include <metadata.h> However, FLAC also ships an <assert.h> header file. If one writes code that wants needs both the Standard C <assert.h&...

...a at mega-nerd.com> wrote: >> Hi, >> >> FLAC helpfully provides a flac.pc file. Unfortunately there is a >> nasty interaction between that file and system header files. >> >> If ones installs flac and relies on pkg-config to find the CFLAGS >> one woulf get CFLAGS value of "-I${includedir}/FLAC" which > suggests >> that FLAC header files like <metadata.h> should be included as: >> >> ? ?#include <metadata.h> >> >> However, FLAC also ships an <assert.h> header file. If one writes &g...

...2 AM, Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > Hi, > > FLAC helpfully provides a flac.pc file. Unfortunately there is a > nasty interaction between that file and system header files. > > If ones installs flac and relies on pkg-config to find the CFLAGS > one woulf get CFLAGS value of "-I${includedir}/FLAC" which suggests > that FLAC header files like <metadata.h> should be included as: > > ? ?#include <metadata.h> > > However, FLAC also ships an <assert.h> header file. If one writes > code that wants needs both t...

...>> Hi, > >> > >> FLAC helpfully provides a flac.pc file. Unfortunately there is a > >> nasty interaction between that file and system header files. > >> > >> If ones installs flac and relies on pkg-config to find the CFLAGS > >> one woulf get CFLAGS value of "-I${includedir}/FLAC" which > > suggests > >> that FLAC header files like <metadata.h> should be included as: > >> > >> ? ?#include <metadata.h> > >> > >> However, FLAC also ships an <assert.h>...

Under Samba 2.2.4 (and possibly earlier), smbpasswd (when run locally) only really reads the first 8 characters, as opposed to the full password. Obviously, this can cause mass confusion. :) The fix is pretty simple (I would offer a diff, but this is the kind of thing the configure script should check for...) - under Solaris getpass() will only return 8 characters - you must use getpassphrase()