search for: uphil

I am running OpenSolaris build 134 on a T1000 (Sparc). It has been an uphill battle getting this far. Many of the commands I find in the various documentation won''t work for me. ------------------------------------------------------------ steve@t1000:~# pfexec pkg install xvm-gui Creating Plan pkg: ''xvm-gui'' matches mu...

...time, status) ~ ph.karno + survival::strata(inst),? data= survival::lung) This fails to give the correct answer because it fools terms(formula, specials= "strata").??? I've stood firm in my response of "that's your bug, not mine", but I begin to believe I am swimming uphill.?? One person responded that it was company policy to qualify everything. I don't see an easy way to fix survival, and even if I did it would be a tremendous amout of work.?? What are other's thoughts? Terry -- Terry M Therneau, PhD Department of Quantitative Health Sciences Mayo...

I am having uphills trying to install P'shop 7 under Wine on a Mac. My initial problem is that I can't understand the log output! Is there a howto for less-than-knowledgeable users about interpreting the logs? And common solutions to errors, too?

I'm just curious to see if I'm fighting an uphill battle that isn't really necessary. Is anyone out there NOT using PAM, running Samba and winbind on Solaris 8? Maybe my problems are related to my attempt to keep it simple and not use pam. -Dan Daniel J. Thomas Systems Administrator Johns Hopkins University Applied Physics Laboratory Laure...

...Disk IPC$ IPC IPC Service (Samba 4.5.1) Domain=[TISSISAT] OS=[Windows 6.1] Server=[Samba 4.5.1] Server Comment --------- ------- Workgroup Master --------- ------- sudo smbclient //tardis/smb/home/phil -Uphil Enter phil's password: session setup failed: NT_STATUS_NO_LOGON_SERVERS [ashanti ~]$ sudo nmblookup 'TISSISAT#1b' 'TISSISAT#1c' 10.2.1.9 TISSISAT<1b> name_query failed to find name TISSISAT#1c [ashanti ~]$ sudo smbclient -d=5 //TARDIS/smb/home/phil -Uphil INFO: Current d...

..., and the plan looks very much like what we would do for Wayland. Is MIR going to be a hard dependency? Is Wayland support going to be dropped from plans? Could it support all 3 systems? Would Wayland related patches be rejected? Working towards getting KDE move towards LightDM has been a constant uphill battle with the politics, and this is just arming everyone with reasons why a LightDM dependency would be bad for us. More warning on this would have been nice. David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/lightdm...

OK. So here's my case: I've been trying to get Samba configured to run as a domain controller for about a month now. The job is to add a domain controller to a workgroup of Windows XP Pro machines. It has been a long uphill struggle with lots of hope but little progress. Just when I was about to give up on Samba, someone suggested that I try in with a few other versions of Windows. 95, 98, NT4 and 2000 run sweetly and readily accept Samba as a domain controller. Shares, users, everything runs beautifully. They can br...

...mal procedure is to not bother, and simply use unencryped private SSH keys. This is, in fact, written into dozens of "chef" and "puppet" system management cookbooks. I've been trying to spend time there trying to provide better handling of private keys, and boy, it's an uphill battle!!! >> If you really want to segregate credentials for different environments > > The agent knows who is asking it about using a key, so you could > certainly have a single agent which applies a policy based on that. > > > //Peter > _______________________________...

...t add at least one register to each register class. > > I'm (just starting) implementing an LLVM target that bares some > similarities to PTX. One of these is the notion of infinite registers, > since my target too is a kind of virtual/universal machine. > It's a bit of an uphill battle since there are places in LLVM that make assumptions about targeting a "real" architecture, to varying degrees. One thing to keep in mind is that the PTX back-end from 3.1 may be a better example to use than the NVPTX back-end in 3.2 and TOT. The original PTX back-end supported...

...ropriate since it >> does not consider metadata to be semantically important for correctness. > > That's a valid point. The OpenCL guys were also discussing metadata > and I think it's fair to consider it a first class citizen. I would like to see that too but it might be an uphill battle. :( > But I also understand perfectly well why it hasn't, so far. Because > metadata is SO generic, if you consider it first-class, people will > start abusing of it for little personal modifications and the IR will > stop being standard and diverge. Absolutely. Even so,...

...ic target option, we could probably move to the patches. I'm in camp (2). Any changes that are not tested are an invitation to upstream developers to "simplify" the code, not knowing that those changes are important. Anyone who commits untested changes to LLVM will inevitably face an uphill battle against benevolent NFC refactorings that break these changes because the expectation of how the code is supposed to behave is not codified in a test. In the short term option (1) sounds more appealing because they can start right away, but I'm going to predict that it will be more expen...

On Wed, Nov 20, 2019 at 12:18 PM Renato Golin <rengolin at gmail.com> wrote: > > On Wed, 20 Nov 2019 at 08:44, Whisperity via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > There *are* open-source Discord clients, 3rd party tools and the like. > > This is a big uphill fight that is rarelly worthy. Not to mention > privacy guarantees and terms and conditions that are not "fixed" by > OSS tooling. > > > The corporation behind Discord is just not authorising you legally to use any of those tools at hand. > > That doesn't sound go...

Hi Justin and all, you've mentioned that you used an easy "trick" for defining an infinite register file in the backend. Does this involve defining a single dummy register, and then adding this dummy reg to each register class? Is anything more needed? I refer to the RegisterInfo.td file, as e.g: llvm-3.0.src/lib/Target/PTX/PTXRegisterInfo.td I'm (just starting)

...they've had enough trouble with > multiple versions; I don't think they want to deal with multiple C++ > ABIs, too. Quite the contrary, knowing that Clang's C++ ABI is completely incompatible with MS is a maintenance *simplification*. Saying that supporting the MS C++ ABI is an uphill battle is an understatement (and better say MS C++ ABI*S*, because it evolved over time and it is known that it will change on future releases.) As far as I'm concerned, I'll never base my decisions on compiler usage on the advertisement of MS compatibility by Clang++, becase I *know* that...

...ompatible name mangling schemes for ABIs that are not guaranteed to be 100% binary compatible is a _feature_, not a bug, since it prevents anyone from even beginning to develop a workflow that relies upon linking possibly incompatible binaries. > > Saying that supporting the MS C++ ABI is an uphill battle is an > understatement (and better say MS C++ ABI*S*, because it evolved over > time and it is known that it will change on future releases.) As far as > I'm concerned, I'll never base my decisions on compiler usage on the > advertisement of MS compatibility by Clang++,...

On 15 February 2011 22:14, David A. Greene <greened at obbligato.org> wrote: > That's why we use { i8, i16 }.  It's not by accident.  We do adhere to > the Itanium ABI. Oh, I see. But the padding is not a problem, it could be [3 x i8] or { i8, i16 }, it doesn't matter, since it's never going to be used. But the [8 x i8] that was the original Base type is, and

...4 -wd4624 ) add_llvm_definitions( -wd4355 -wd4715 -wd4180 -wd4345 -wd4224 ) add_llvm_definitions( -wd4351 ) It's very likely that some of those warnings are really useful (i.e. are hinting at bugs.) OTOH, keeping LLVM warning-free for VC++ and gcc at the same time looks like a never-ending uphill battle. -- Óscar

...ally surprised that the change to support those ABI constraints wasn't too big... >> That's a valid point. The OpenCL guys were also discussing metadata >> and I think it's fair to consider it a first class citizen. > > I would like to see that too but it might be an uphill battle.  :( Maybe even steeper than introducing new fields to the IR... >> But that unleashes a completely different beast that I'm not willing >> to handle right now... ;) > > Oh, come on!  Where's your sense of adventure?  :) :D One thing at a time... It's in m...

...ebugging information can be extracted, I have to assume. A working example as I have asked for above would probably help me alot. thanks! --Tim If opportunity doesn't knock, build a door. "I can" is a way of life. More and Bigger is not always Better. The road to success is always uphill. ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

...though I can't get the rquota-rquotad patch to build on Solaris I have found some code on the net which does do RPC based quota lookups. I'm toying with the idea of trying to modify rquota-rquotad to use this other code. However this is out of my area of knowledge so it will be an uphill battle ... so if reading quotas from NFS-mounted filestores will be coming Real Soon Now I'll probably just wait instead. So any ideas as to timescales, please? Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-190...