similar to: Compiling Samba4 RC3 on AIX 6.1 with IBM vac

Displaying 20 results from an estimated 1000 matches similar to: "Compiling Samba4 RC3 on AIX 6.1 with IBM vac"

2017 Jun 10
0
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 10/06/2017 17:23, Michael Felt wrote: > On 10/06/2017 14:42, Michael Felt wrote: >> >> Next chapter in packaging.(Not meant to be extensive, only what I run >> across and is easy to report) > > c) > > 378 | int quota_root_default_init(struct quota_root *root, const > char *args, > 379 | const char **error_r) >
2017 Jun 10
1
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 10/06/2017 17:26, Michael Felt wrote: > On 10/06/2017 17:23, Michael Felt wrote: >> On 10/06/2017 14:42, Michael Felt wrote: >>> >>> Next chapter in packaging.(Not meant to be extensive, only what I >>> run across and is easy to report) So, now in an attempt to report on where I am at... michael at
2017 Jun 10
0
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 09/10/2016 21:48, Michael Felt wrote: > I finally decided it was really time to stop being lazy and really > move away from gmail. After I have a server in my basement using > power, etc. > > So I turned on the imap provided - and did not quite cry - it will > have to do for now, but imap2 is wanting. Next chapter in packaging. a) I have 'patched' several files to
2017 Jun 10
2
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 10/06/2017 14:42, Michael Felt wrote: > > Next chapter in packaging.(Not meant to be extensive, only what I run > across and is easy to report) c) 378 | int quota_root_default_init(struct quota_root *root, const char *args, 379 | const char **error_r) 380 | { 381 | const struct quota_param_parser default_params[] = {
2016 Oct 09
6
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
Hi. I finally decided it was really time to stop being lazy and really move away from gmail. After I have a server in my basement using power, etc. So I turned on the imap provided - and did not quite cry - it will have to do for now, but imap2 is wanting. A real server yes, but not Linux. (Using linux would require another server AND I would feel I am being lazy again). So, I downloaded
2016 Oct 10
4
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 10-Oct-16 06:45, Aki Tuomi wrote: > Does your build end at some particular point? See **** DETAILS **** for in depth (I hope enough!) study/report. > > Aki I would guess this is not "c99" way... Making all in lib-http source='test-http-auth.c' object='test-http-auth.o' libtool=no DEPDIR=.deps depmode=xlc /bin/sh ../../depcomp xlc_r
2016 Oct 10
4
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 09-Oct-16 22:51, Aki Tuomi wrote: >> >> Michael > > Does the compiler support C99 standard? > > Aki Yes. Plus extended features. Key difference with GCC, e.g., are the flags to the compiler, but autotools general manages those well. Key difference with platform (well, of of) is that it is not GNU, and how shared libraries are built. Again, libtool in particular,
2008 Jan 30
0
Anybody have expirience with Powercom Imperial 1500 VAC (USB interface)?
Hello ! Anybody have expirience with Powercom Imperial 1500 VAC (USB interface) ? Under FreeBSD 6.2 it's shown as uhid device: uhid0: POWERCOM CO., LTD. USB to Serial, rev 1.00/0.00, addr 2, iclass 3/0 usbhid-ups doesn't recognize it, and powercom driver doesn't work with uhid device. It seems for me that FreeBSD doesn't support it, so it doesn't create serial device for
2017 May 22
0
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
Hi Micheal, I am currently working on AIX + VAC + NTPv4 build. and I have also faced same issues as mentioned by you in link https://www.dovecot.org/list/dovecot/2016-October/105597.html Wondering if you have got any resolution for above issue. If yes, please help me with your guidance. thanks in advance, seema
2017 Jun 06
0
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 09/10/2016 21:48, Michael Felt wrote: > > A real server yes, but not Linux. (Using linux would require another > server AND I would feel I am being lazy again). Well, I have been busy, and it is time to force move dovecot forward. Being 'lazy' I am doing some initial tests on my POWER platform using an old debian distro to build the latest (via git). That has been
2017 Jun 07
1
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 06.06.2017 21:30, Michael Felt wrote: > On 09/10/2016 21:48, Michael Felt wrote: >> >> A real server yes, but not Linux. (Using linux would require another >> server AND I would feel I am being lazy again). > > Well, I have been busy, and it is time to force move dovecot forward. > > Being 'lazy' I am doing some initial tests on my POWER platform using
2002 Jul 16
2
scale parameter and parameter vac-cov matrix in GEE
Dear all, It looks like the parameters var-cov matrix returned by gee() is not adjusted for the scale parameter: > fm1 <- gee(nbtrp ~ strate * saison + offset(log(surf)), family = poisson, data = Eff2001, + id = loc, tol = 1e-10, corstr = "exchangeable") [1] "Beginning Cgee S-function, @(#) geeformula.q 4.13 98/01/27" [1] "running glm to get initial
2020 Aug 15
5
Supporting libunwind on Windows 10 (32bit; 64bit) for MSVC and Clang
Hello. I was trying to compile https://github.com/llvm/llvm-project/tree/master/libunwind using: - MSVC - Clang I wasn't able to configure this project for using MSVC (directly or via clang-cl): >cmake -G Ninja -DLLVM_PATH="C:/Users/clang/llvm-project-10.0.1/llvm" -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX="C:\Users\clang\libunwind_llvm" ../libunwind --
2016 Oct 10
3
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 10/10/2016 14:59, Stephan Bosch wrote: > > > Op 10-10-2016 om 14:39 schreef Michael Felt: >> On 10-Oct-16 06:45, Aki Tuomi wrote: >>> Does your build end at some particular point? >> See **** DETAILS **** for in depth (I hope enough!) study/report. >>> >>> Aki >> >> I would guess this is not "c99" way... > > It seems to
2015 Feb 24
2
Call for testing: OpenSSH 6.8
On Tue, 24 Feb 2015, Kevin Brott wrote: > > On Mon, Feb 23, 2015 at 4:53 PM, Damien Miller <djm at mindrot.org> wrote: > > This should fix it: > > diff --git a/regress/netcat.c b/regress/netcat.c > index 84efe11..4b8c51c 100644 > --- a/regress/netcat.c > +++ b/regress/netcat.c > [sniip] > > > > This patch
2006 Feb 21
2
building in AIXV5.3 using the IBM C for AIX compiler V6.0
What fun. I don't often stoke up the boiler and actually compile open-source code, but here I am at the beginning of just such a joyous and wondrous adventure. I'm running the latest level of AIX (V5.3...V4.3 has been obsolete for at least, what, 5 years) and using the IBM compiler (xlc is similarly obsolete, from back when the compiler came with the O/S...oh, for the halcyon days of
2016 Dec 23
2
3.9 regression with legacy static assert macros (bad type resolution)
3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: #define COMPILE_TIME_ASSERT( expr ) \ extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) ); I notice that the issue is fixed on current trunk. Does anyone know what revision introduced the fix? Can we get it
2006 Oct 18
1
nut 2.0.4 won't compile on AIX 5.3
Hi there, I'm trying to compile nut 2.0.4 on an AIX 5.3 machine, but it fails: $ make common/ /usr/vac/bin/cc -I../include -O -c common.c /usr/vac/bin/cc -I../include -O -c upsconf.c /usr/vac/bin/cc -I../include -O -c parseconf.c /usr/vac/bin/cc -I../include -O -c state.c Target "all" is up to date. drivers/ /usr/vac/bin/cc -I../include -O -c
2008 Oct 02
1
[LLVMdev] MS C++ gives error C2371 on this code while (obviously)gcc compiles it fine
Ah, interesting, have not ran across that before (as I always strive to never use the same name as any scope previously), but rather interesting that GCC gets it wrong while VC++ gets it right, kind of a switch. And yes, that switch I mentioned is for VC6 style in VC7.1 (what I use), you have to switch it to make it conformant, nice to hear VC8 does it correctly by default now. On Thu, Oct 2,
2016 Dec 23
0
3.9 regression with legacy static assert macros (bad type resolution)
> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: > > #define COMPILE_TIME_ASSERT( expr ) \ > extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( (