Re: [Bacula-users] Problems starting Bacula aftercompilingandinstalling
2009-01-21 11:33:24
Hi Timo:
I found a message[1] from myself but I can't find the Developers section in
Wiki. Can you help me?
[1]
http://sourceforge.net/mailarchive/message.php?msg_id=49115117.2090200%40ioda-net.ch
Ing. Reynier Pérez Mira
Dirección Técnica IP
> -----Original Message-----
> From: Timo Neuvonen [mailto:timo-news AT tee-en DOT net]
> Sent: Wednesday, January 21, 2009 11:06 AM
> To: bacula-users AT lists.sourceforge DOT net
> Subject: Re: [Bacula-users] Problems starting Bacula
> aftercompilingandinstalling
>
> "Reynier Perez Mira" <rperezm AT uci DOT cu> kirjoitti viestissä
> news:4D18382A12A9B64190E1AD825FB591F3019E90DE AT ucixw2.uci DOT cu...
> > > Search in the wiki & ml about the CX FLAGS D_FORTIFY_SOURCE=0
> > >
> > > Also there's explaination in the changelog of rpms sources
> > > made by Scott.
> >
> > Hi Bruno and thanks for your reply:
> > I search in Wiki and Bacula Installation and Configuration Manual as you
> > suggested me but I can't find nothing. Maybe I not know how to find. Also
> > I read the Changelog file in the rpms sources and I can't find nothing.
> > Any help?
>
> I think you need to give that fortify_source stuff as an extra option to the
> compiler, but the exact syntax for your system may require some tuning. What
> you can find from rpm release notes (copypasted below) won't propably be
> a complete out-of-the-box solution for a non-rpm system that you obviously
> have. But it should at least give a hint what to keep looking for, and a
> short explanation what (new enough glibc version) is causing this.
>
> Regards,
> Timo
>
>
>
> *****************************************
> * Buffer Overflow Error and Crash in fd *
> *****************************************
>
> Fedora 8/9 now set -D_FORTIFY_SOURCE=2 as default compiler option. This
> will probably be true on other platforms as they move to glibc >= 2.7. This
> causes a false "buffer overflow detected" error and crash in bacula-fd and
> other executables.
>
> To avoid this problem a workaround for Redhat platforms is to set the CFLAGS
> in your ~/.rpmmacros file as follows:
>
> # uncomment for bacula
> #%__global_cflags -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=0 -fno-
> exceptions
> -fno-strict-aliasing -fno-rtti
>
> For SuSE platforms set as follows in your ~/.rpmrc file:
>
> optflags:
> i586 -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -
> D_FORTIFY_SOURCE=0
> optflags: x86_64 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=0
>
> See the discussion thread on bacula-devel for more information:
> http://sourceforge.net/search/?ml_name=bacula-
> devel&type_of_search=mlists&group_id=50727&words=%22buffer+overflow+
> detected%22
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
|
|