Hi
I'm really sorry, but it seems like this is just completely my own fault.
Apparently MS-Windows works around this issue by preventing people from
creating accounts with the same name as the
machine.
When I installed this machine and ran into that, I assumed it was a bug and
found a way to for
Hi
Thanks for the patch, but no, it doesn't fix the problem.
Going home now, but I'll be available tomorrow if you have any more ideas for
me to try out :-)
Thanks, Noel Grandin
Tor Lillqvist wrote:
>> This appears to be a windows weirdity related to the fact that my account
>> name and my mac
> This appears to be a windows weirdity related to the fact that my account
> name and my machine name is the same.
> Under this situation, the LookupAccountName API call will return the wrong
> answer.
Well, "wrong" or "right" is a matter of opinion here, I guess... The
documentation doesn't e
Hi
This appears to be a windows weirdity related to the fact that my account name
and my machine name is the same.
Under this situation, the LookupAccountName API call will return the wrong
answer.
See here:
http://archives.neohapsis.com/archives/ntbugtraq/1998-1999/msg00516.html
Regards, Noel.
> strUserID: S-1-5-21-3395787511-4075999146-953599952
> comes from qa/osl/security/osl_Security.cxx
>
> strID: S-1-5-21-3395787511-4075999146-953599952-1000
> comes from osl/w32/security.c
Hmm, for me, if I add code to just print out the aMessage even if the assertion
doesn't fail, I see:
strUs
I stuck some debug in the relevant code, and
dwSubAuthorities==5 in security.c
dwSubAuthorities==4 in osl_Security.cxx
So this could be some weird Windows thing because the two modules are using
different API calls to retrieve the SID.
Caolán McNamara wrote:
> On Wed, 2011-08-31 at 14:53 +0200
On Wed, 2011-08-31 at 14:53 +0200, Noel Grandin wrote:
> New build log attached.
strUserID: S-1-5-21-3395787511-4075999146-953599952
comes from qa/osl/security/osl_Security.cxx
strID: S-1-5-21-3395787511-4075999146-953599952-1000
comes from osl/w32/security.c
so its a matter of seeing which one
Wow! thanks for the quick response. New build log attached.
This is a 32-bit Windows7-Ultimate machine (fully up to date), if that makes
any difference.
Thanks, Noel Grandin
Caolán McNamara wrote:
> On Wed, 2011-08-31 at 14:16 +0200, Noel Grandin wrote:
>> I've attached the build log file for t
On Wed, 2011-08-31 at 14:16 +0200, Noel Grandin wrote:
> I've attached the build log file for that subcomponent.
>
> Test name: osl_Security::getUserIdent::getUserIdent_001
> assertion failed
> - Expression: ( sal_True == strUserID.equals( strID ) ) && ( sal_True
> == bRes )
> - #test comment#:
I've attached the build log file for that subcomponent.
Regards, Noel Grandin
Tor Lillqvist wrote:
>> (1) I had to comment out some code in qa\osl\security\osl_Security.cxx
>> because it was trying to run a unit test which
>> failed because I'm not logged in as Administrator.
> Are you sure? Wh
> (1) I had to comment out some code in qa\osl\security\osl_Security.cxx
> because it was trying to run a unit test which
> failed because I'm not logged in as Administrator.
Are you sure? What was the exact failure message you got?
> Perhaps it should skip that test if the currently logged in u
Thanks, it's getting further now, but still throwing the same linker error when
linking "ulfex.exe"
-- Noel
Caolán McNamara wrote:
> On Wed, 2011-08-31 at 12:04 +0200, Noel Grandin wrote:
>> (3) Right now I'm struggling to get past a link error in l10ntools
>> helpmerge.obj : error LNK2019: unre
On Wed, 2011-08-31 at 12:04 +0200, Noel Grandin wrote:
> (3) Right now I'm struggling to get past a link error in l10ntools
> helpmerge.obj : error LNK2019: unresolved external symbol
> "__declspec(dllimport) class rtl::OString __cdecl
> comphelper::string::getToken(class rtl::OString const &,long,
Thanks, you're right, with one repo, the checkout and build process is
definitely much smoother!
(1) I had to comment out some code in qa\osl\security\osl_Security.cxx because
it was trying to run a unit test which
failed because I'm not logged in as Administrator.
Perhaps it should skip that te
> Are there up-to-date instructions somewhere for building on Windows with the
> new OneGit repos?
Well, the aspects that changed with the switch from several git repos to just
one (or two, or three, depending on whether you want to include help and
dictionaries or not) don't differ between pla
Hi
Are there up-to-date instructions somewhere for building on Windows with the
new OneGit repos?
I seem to be stuck building on the old repos.
Thanks, Noel Grnadin
Disclaimer: http://www.peralex.com/disclaimer.html
___
LibreOffice mailing list
Libr
16 matches
Mail list logo
