search for: scandium

...module error" and "NT_STATUS_LOGON_TYPE_NOT_GRANTED" messages. I've been on this for 2 full days now, I've tried everything I could think of. Any help would be appreciated. Regards, Dan O'Brien (conf files and messaeges below) /var/log/messages ... May 21 16:58:13 scandium winbindd[14882]: [2007/05/21 16:58:13, 0] libsmb/smb_signing.c:signing_good(240) May 21 16:58:13 scandium winbindd[14882]: signing_good: BAD SIG: seq 1 May 21 16:58:13 scandium winbindd[14882]: [2007/05/21 16:58:13, 0] libsmb/clientgen.c:cli_receive_smb(121) May 21 16:58:13 scandium winbindd[1488...

On Wed, Nov 15, 2017 at 10:45 PM, N <scandium at me.com> wrote: > > You can't really remove any native linker-compatible command line > interface unless you get agreement from all parties including Microsoft and > Apple to switch to the GNU command line as the universal interface in the > future versions of their toolcha...

On Mon, Nov 13, 2017 at 9:31 PM, N <scandium at me.com> wrote: > > For example, MSVC link.exe doesn't have --start-group and --end-group > options because their symbol resolution semantics are different than Unix. > > Yes, but this is specific for a linker, not for a target. For example, GNU > ld supports this option...

...Darwin driver. As to why there's no driver that provides a unified command line arguments, I can't speak for other people. But no one seems to have been interested in it enough to actually invent and implement a set of unified command line arguments. On Thu, Oct 26, 2017 at 2:20 PM, N <scandium at me.com> wrote: > > I think using ld.lld or lld-link is preferred way over "lld -flavor gnu" > or "lld -flavor link". > > -flavor seems to be still actively used in Clang… By the the way, there > seems to be no special > command name for Darwin targets...

...Darwin driver. As to why there's no driver that provides a unified command line arguments, I can't speak for other people. But no one seems to have been interested in it enough to actually invent and implement a set of unified command line arguments. On Thu, Oct 26, 2017 at 2:20 PM, N <scandium at me.com> wrote: > > I think using ld.lld or lld-link is preferred way over "lld -flavor gnu" > or "lld -flavor link". > > -flavor seems to be still actively used in Clang… By the the way, there > seems to be no special > command name for Darwin targets...

...s to why there's no driver that provides a unified command line arguments, I can't speak for other people. But no one seems to have been interested in it enough to actually invent and implement a set of unified command line arguments. >> >> On Thu, Oct 26, 2017 at 2:20 PM, N <scandium at me.com> wrote: >>> I think using ld.lld or lld-link is preferred way over "lld -flavor gnu" or "lld -flavor link". >> >> -flavor seems to be still actively used in Clang… By the the way, there seems to be no special >> command name for Darwin tar...

...at provides a unified command line > arguments, I can't speak for other people. But no one seems to have been > interested in it enough to actually invent and implement a set of unified > command line arguments. > >>> > >>> On Thu, Oct 26, 2017 at 2:20 PM, N <scandium at me.com> wrote: > >>>> I think using ld.lld or lld-link is preferred way over "lld -flavor > gnu" or "lld -flavor link". > >>> > >>> -flavor seems to be still actively used in Clang… By the the way, > there seems to be no special...

Hi all, According to lld/docs/Driver.rst, Flavor command line option determines the style of lld command-line interface when invoked. However, it looks like this option also determines the set of supported targets we are linking for. For example, lld -flavor gnu cannot link mach-o binaries, and could not link PE binaries either (well, not until rL312926). Is this really intended by the design