Re: [Bacula-users] Bacula 9.x.x and Solaris 11.3 (and OpenSUSE)...

2018-04-11 Thread Dimitri Maziuk 

On 2018-04-11 03:52, Radosław Korzeniewski wrote:

I'm very surprised that your build is not working and you have to 
disable libtool. Unfortunate I never tried Solaris Compiler Suite with 
Bacula.


I haven't used solaris in forever but back when, libtool did not work 
with Sun's CC. Linker commands, options, and everything else libtool 
does was simply wrong for Studio toolchain, linking step failed every time.


Dima

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.x.x and Solaris 11.3 (and OpenSUSE)...

2018-04-11 Thread Radosław Korzeniewski 
Hello,

I'm building Bacula 9.0.6 on Solaris 11 using gcc (I'm not sure if I used
gcc provided by Oracle or installed externally) and the following configure
(which forces 64bit compilation and debugging symbols):

CXXFLAGS="-m64 -g" CFLAGS="-m64 -g" LDFLAGS="-m64 -g" ./configure
--prefix=/export/home/radekk/bacula
--with-working-dir=/export/home/radekk/bacula/working
--with-pid-dir=/export/home/radekk/bacula/working
--with-subsys-dir=/export/home/radekk/bacula/subsys --with-postgresql
--enable-smartalloc --enable-lockmgr
--with-logdir=/export/home/radekk/bacula/log

I'm very surprised that your build is not working and you have to disable
libtool. Unfortunate I never tried Solaris Compiler Suite with Bacula. I
have to check if I have access to it.

best regards

2018-04-06 14:53 GMT+02:00 Gary R. Schmidt :

> On 06/04/2018 18:40, Daniel Heitepriem wrote:
>
>> Hi Gary,
>>
>> I just tried to compile 9.0.6 on a Solaris 11.3 box (but using GCC 5.4.0
>> and MySQL) with these options:
>>
>> CFLAGS="-g -m64" LDFLAGS="-m64" CXXFLAGS="-m64" ./configure \
>> --prefix=/opt/bacula \
>> --with-dir-user=bacula \
>> --with-dir-group=bacula \
>> --with-sd-user=bacula \
>> --with-sd-group=bacula \
>> --with-fd-user=root \
>> --with-fd-group=bacula \
>> --enable-smartalloc \
>> --sbindir=/opt/bacula/bin \
>> --sysconfdir=/opt/bacula/etc \
>> --with-subsys-dir=/opt/bacula/var \
>> --with-working-dir=/opt/bacula/var/bacula/working \
>> --with-pid-dir=/opt/bacula/var \
>> --with-logdir=/opt/bacula/var \
>> --with-archivedir=/opt/bacula/var \
>> --with-mysql=/opt/mysql \
>> --with-openssl
>>
>> and it's working fine so far. Your issue may be related to the
>> "disable-libtool" parameter you provided. Can you try to build it
>> without this disable parameter.
>>
>> Thank you Daniel, removing "--disable-libtool" allowed it to build, why
> whoever disabled it didn't make configure barf on it is something I can
> only wonder about.
>
> And in some further fiddling about I found that replacing "NO_ECHO = @"
> with "NO_ECHO =" in the makefiles makes it *much* easier to work out just
> what is going wrong.  Hiding information just makes life difficult.
>
>
> Cheers,
> GaryB-)
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>



-- 
Radosław Korzeniewski
rados...@korzeniewski.net
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.x.x and Solaris 11.3 (and OpenSUSE)...

2018-04-06 Thread Gary R. Schmidt 

On 06/04/2018 18:40, Daniel Heitepriem wrote:

Hi Gary,

I just tried to compile 9.0.6 on a Solaris 11.3 box (but using GCC 5.4.0
and MySQL) with these options:

CFLAGS="-g -m64" LDFLAGS="-m64" CXXFLAGS="-m64" ./configure \
--prefix=/opt/bacula \
--with-dir-user=bacula \
--with-dir-group=bacula \
--with-sd-user=bacula \
--with-sd-group=bacula \
--with-fd-user=root \
--with-fd-group=bacula \
--enable-smartalloc \
--sbindir=/opt/bacula/bin \
--sysconfdir=/opt/bacula/etc \
--with-subsys-dir=/opt/bacula/var \
--with-working-dir=/opt/bacula/var/bacula/working \
--with-pid-dir=/opt/bacula/var \
--with-logdir=/opt/bacula/var \
--with-archivedir=/opt/bacula/var \
--with-mysql=/opt/mysql \
--with-openssl

and it's working fine so far. Your issue may be related to the
"disable-libtool" parameter you provided. Can you try to build it
without this disable parameter.

Thank you Daniel, removing "--disable-libtool" allowed it to build, why 
whoever disabled it didn't make configure barf on it is something I can 
only wonder about.


And in some further fiddling about I found that replacing "NO_ECHO = @" 
with "NO_ECHO =" in the makefiles makes it *much* easier to work out 
just what is going wrong.  Hiding information just makes life difficult.


Cheers,
GaryB-)

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.x.x and Solaris 11.3 (and OpenSUSE)...

2018-04-06 Thread Daniel Heitepriem 
Hi Gary,

I just tried to compile 9.0.6 on a Solaris 11.3 box (but using GCC 5.4.0
and MySQL) with these options:

CFLAGS="-g -m64" LDFLAGS="-m64" CXXFLAGS="-m64" ./configure \
--prefix=/opt/bacula \
--with-dir-user=bacula \
--with-dir-group=bacula \
--with-sd-user=bacula \
--with-sd-group=bacula \
--with-fd-user=root \
--with-fd-group=bacula \
--enable-smartalloc \
--sbindir=/opt/bacula/bin \
--sysconfdir=/opt/bacula/etc \
--with-subsys-dir=/opt/bacula/var \
--with-working-dir=/opt/bacula/var/bacula/working \
--with-pid-dir=/opt/bacula/var \
--with-logdir=/opt/bacula/var \
--with-archivedir=/opt/bacula/var \
--with-mysql=/opt/mysql \
--with-openssl

and it's working fine so far. Your issue may be related to the
"disable-libtool" parameter you provided. Can you try to build it
without this disable parameter.

Regards,
Daniel

On 06.04.18 09:34, Gary R. Schmidt wrote:
> ...Or, Bacula is getting about as portable as the Great Wall of China.
>
> Trying to build Bacula on Solaris 11.3 x64, attempted using both the
> Solaris Compiler Suite (now known as Developer Studio) and GCC 7.3.0.
>
> TL;DR - it doesn't build, because of stupidity(TM).
>
> So, I have a chance to upgrade my Bacula infrastructure, and move the
> tape loader onto honking great big box with 100+Gb of RAM and stuff,
> so I thinks, "I'll switch to PostgreSQL, and in the same step, update
> from 7.0.5 to 9.0.6".
>
> Pull the new version down, set up configure, thusly (Yes, I know
> --disable-libtool is a noop now, that's just another stupidity(TM)):
> $
> PATH=/opt/postgres/bin:/usr/bin:/bin:/opt/solarisstudio12.4/bin:/opt/sfw/bin:/usr/ccs/bin:/opt/local/bin:/usr/openwin/bin:.
> $ export PATH
> $ ./configure \
>     CC=cc CXX=CC \
>     CFLAGS="-g -O -m64" \
>     LDFLAGS="-m64" \
>     --prefix=/opt/bacula \
>     --with-archivedir=/opt/bacula/archive \
>     --with-working-dir=/home/bacula/working \
>     --with-plugindir=/opt/bacula/plugins \
>     --with-scriptdir=/opt/bacula/scripts \
>     --with-subsys-dir=/opt/bacula/subsys \
>     --with-postgresql=/opt/postgres \
>     --with-dir-user=bacula \
>     --with-dir-group=backup \
>     --with-sd-user=bacula \
>     --with-sd-group=backup \
>     --with-fd-user=root \
>     --with-fd-group=backup \
>     --enable-smartalloc \
>     --enable-lockmgr \
>     --enable-batch-insert \
>     --with-dump-email=m...@me.me \
>     --with-job-email=m...@me.me \
>     --disable-libtool \
>     --with-x \
>     --x-includes=/usr/include/X11 \
>     --with-smtp-host=mail
>
> Not a problem, all looks copacetic.
>
> $ gmake
> ...
> "fd_plugins.h", line 200: Warning: Identifier expected instead of "}".
>
> Sigh, that's just an annoyance, but as I learnt my C back when K
> Edition 1 was the bible, it niggles me, so I fixes it, just removing
> the unneeded , before the }.
>
> So, onwards.
> ...
> Making libbacsd.la ...
> /opt/solarisstudio12.4/bin/CC   -m64 -o libbacsd.la \
>    acquire.lo ansi_label.lo askdir.lo autochanger.lo block.lo
> block_util.lo butil.lo dev.lo device.lo ebcdic.lo init_dev.lo label.lo
> lock.lo match_bsr.lo mount.lo null_dev.lo os.lo parse_bsr.lo read.lo
> read_records.lo record_read.lo record_util.lo record_write.lo
> reserve.lo scan.lo sd_plugins.lo spool.lo tape_alert.lo vol_mgr.lo
> wait.lo fifo_dev.lo file_dev.lo tape_dev.lo vtape_dev.lo \
>   -export-dynamic -rpath /opt/bacula/lib -release 9.0.6
> CC: Warning: Option -path passed to ld, if ld is invoked, ignored
> otherwise
> ld: fatal: option '-export-dynamic' and option '-elease' are incompatible
> ld: fatal: option '-export-dynamic' is incompatible with building a
> relocatable object
> ld: fatal: option '-path' is incompatible with building a relocatable
> object
> ld: fatal: option '-R/opt/solarisstudio12.4/lib/amd64' is incompatible
> with building a relocatable object
> gmake[1]: *** [libbacsd.la] Error 2
> gmake[1]: Leaving directory
> `/home/garys/src/bacula/bacula-9.0.6/src/stored'
>
> Now *that's* useful, not.  Looks like someone is trying to build a
> shared object with the wrong extension, using the linker.  Oh, and
> they think the linker is the GNU linker.  No, it isn't, and way back
> in the configure process it worked that out.
>
> Just for fun, I removed the "-rpath /opt/bacula/lib -release 9.0.6"
> and tried again...
> ...
> Making libbacsd.la ...
> /opt/solarisstudio12.4/bin/CC   -m64 -o libbacsd.la \
>    acquire.lo ansi_label.lo askdir.lo autochanger.lo block.lo
> block_util.lo butil.lo dev.lo device.lo ebcdic.lo init_dev.lo label.lo
> lock.lo match_bsr.lo mount.lo null_dev.lo os.lo parse_bsr.lo read.lo
> read_records.lo record_read.lo record_util.lo record_write.lo
> reserve.lo scan.lo sd_plugins.lo spool.lo tape_alert.lo vol_mgr.lo
> wait.lo fifo_dev.lo file_dev.lo tape_dev.lo vtape_dev.lo \
>   -export-dynamic
> ld: fatal: file acquire.lo: open failed: No such file or directory
> ld: fatal: file