Displaying 20 results from an estimated 7000 matches similar to: "Building QT on CentOS 5"
2010 Mar 27
2
Network tuning for working with very old Solaris
G'day.
I am trying to get a very old Solaris 5.7 server to ftp data to my
updated CentOS 5.4 server but the Solaris box keeps losing
networking after sending some data. I can't ping the Solaris box
from any of the servers on my network.
Could this be related to a much newer (modern) TCP/IP stack in
Linux and TCP options? If so, does anyone have any suggestions
for how I can tune the
2014 May 14
1
Error starting Virtual Machine Manager: Failed to contact configuration server
I just updated and rebooted a VM host server which
runs CentOS 6.5/x86_64. After rebooting, I can't start the
virtual-manager due to the error:
Error starting Virtual Machine Manager: Failed to contact configuration
server; some possible causes are that you need to enable TCP/IP networking
for ORBit, or you have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ [^]
2011 Jun 28
2
OpenOffice 3.3.0 crashing on CentOS 5.5
The last few releases of OpenOffice have gotten very
unstable on my desktop which is a CentOS 5.5 i386 system.
After multiple crashes when doing embedded simple drawings
in OpenOffice writer (circles and lines with connections), I
started using the versions from Sun then Oracle. I am
now using version 3.3: openooffice.org3-3.3.0-9567. I've
lived with this but with version 3.x it has gotten
2011 Oct 05
3
Firefox 7 on CentOS 5
Anyone have any luck running updated Firefox
on CentOS 5? We have CentOS 5 workstations
and need to update their Firefox but it dumps
core even when using the libstdc++ from Fedora 9.
I would like anything stable and secure beyond
Firefox 3 but can't find tarballs for anything
other than 7.0.1.
CentOS 5.5 i386 w/ updates
firefox-7.0.1.tar.bz2
libstdc++-4.3.0-8.i386.rpm from Fedora 9
2012 May 01
2
[LLVMdev] Gold plugin and LLVM tools documentation
Hi,
I've been following the instructions on how to use the LLVM Gold
plugin at http://llvm.org/docs/GoldPlugin.html while building an
multiple versions of WebKit. The documentation hasn't been updated
since 2010 and hasn't really matched my experiences, so I'd like to
ask if I'm doing these steps incorrectly. What I'm trying to do is
force all compilation steps to
2012 May 01
0
[LLVMdev] Gold plugin and LLVM tools documentation
> First, I create libjscore.a with ar, where I've changed the command
> line to load the plugin:
> ar cqs --plugin
> /home/tmjackso/multicompiler/llvm-3.0/release/lib/LLVMgold.so
> libjscore.a <list of object files>
Note that you shouldn't need to pass --plugin to ar, it searches bfd-plugins.
> Then I link jsc against libjscore.a:
>
1997 Sep 21
1
Active X versus Java, Linux versus NT
Having recently read about the lack of security
of Active X controls, I was wondering if I could
get some specifics about its lack of security
versus the security of JAVA. Also about the
security of JAVA under Linux. I understand that
MS''s concept of security is a) investigate the
vendor, b) issue a certificate of authority, 3)
vendor is now trused to do anything (fox guarding
the hen
2013 Jun 24
1
Best solution for TRIM on CentOS 5.x
I am planning on using solid state disks with my CentOS 5.x
systems. Currently, I am using EXT3 for the file system.
>From what I can find, CentOS 5.x does not support TRIM
on solid state disks? Is this correct?
Should I obtain and build the updated hdparm and use that
to trim my drives (for example, via CRON every night at midnight)?
Or should I get fstrim (updated util-linux)?
Any other
2013 Oct 18
0
[LLVMdev] [RFC] Stackmap and Patchpoint Intrinsic Proposal
On Oct 18, 2013, at 10:09 AM, Hal Finkel <hfinkel at anl.gov> wrote:
> ----- Original Message -----
>>
>> On Fri, Oct 18, 2013 at 1:39 AM, Andrew Trick < atrick at apple.com >
>> wrote:
>>
>>
>>
>> The initial documentation and patches name these intrinsics in a
>> "webkit" namespace. This clarifies their current purpose
2013 Oct 18
3
[LLVMdev] [RFC] Stackmap and Patchpoint Intrinsic Proposal
----- Original Message -----
>
> On Fri, Oct 18, 2013 at 1:39 AM, Andrew Trick < atrick at apple.com >
> wrote:
>
>
>
> The initial documentation and patches name these intrinsics in a
> "webkit" namespace. This clarifies their current purpose and conveys
> that they haven't been standardized for other JITs yet. If someone on
> the on the dev
2016 Feb 16
2
WebKit B3 (was LLVM Weekly - #110, Feb 8th 2016)
> On Feb 15, 2016, at 4:25 PM, Philip Reames <listmail at philipreames.com> wrote:
>
> After reading https://webkit.org/blog/5852/introducing-the-b3-jit-compiler/ <https://webkit.org/blog/5852/introducing-the-b3-jit-compiler/>., I jotted down a couple of thoughts of my own here: http://www.philipreames.com/Blog/2016/02/15/quick-thoughts-on-webkits-b3/
2016 Feb 16
2
WebKit B3 (was LLVM Weekly - #110, Feb 8th 2016)
> On Feb 15, 2016, at 5:34 PM, Philip Reames <listmail at philipreames.com> wrote:
>
>
>
> On 02/15/2016 04:57 PM, Andrew Trick wrote:
>>
>>> On Feb 15, 2016, at 4:25 PM, Philip Reames < <mailto:listmail at philipreames.com>listmail at philipreames.com <mailto:listmail at philipreames.com>> wrote:
>>>
>>> After reading
2016 Feb 15
5
WebKit B3 (was LLVM Weekly - #110, Feb 8th 2016)
> On Feb 9, 2016, at 9:55 AM, Rafael Espíndola via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> >
> > JavaScriptCore's [FTL JIT](https://trac.webkit.org/wiki/FTLJIT <https://trac.webkit.org/wiki/FTLJIT>) is moving away
> > from using LLVM as its backend, towards [B3 (Bare Bones
> > Backend)](https://webkit.org/docs/b3/
2013 Oct 18
4
[LLVMdev] [RFC] Stackmap and Patchpoint Intrinsic Proposal
On Oct 18, 2013, at 11:08 AM, Andrew Trick <atrick at apple.com> wrote:
>>
>> I recommend, this being the case, to replace 'webkit' with 'experimental'. Having webkit in the name implies some dependence on webkit, and there is none. Plus, this functionality will be used by outside projects as soon as it lands in trunk, and I suspect that having webkit in the
2013 Oct 18
0
[LLVMdev] [RFC] Stackmap and Patchpoint Intrinsic Proposal
On Fri, Oct 18, 2013 at 1:39 AM, Andrew Trick <atrick at apple.com> wrote:
>
> The initial documentation and patches name these intrinsics in a
> "webkit" namespace. This clarifies their current purpose and conveys
> that they haven't been standardized for other JITs yet. If someone on
> the on the dev list says "yes we want to use these too, just the way
2013 Oct 19
1
[LLVMdev] [RFC] Stackmap and Patchpoint Intrinsic Proposal
On Oct 18, 2013, at 2:59 PM, Evan Cheng <evan.cheng at apple.com> wrote:
>
> On Oct 18, 2013, at 12:39 PM, Chris Lattner <clattner at apple.com> wrote:
>
>> On Oct 18, 2013, at 11:08 AM, Andrew Trick <atrick at apple.com> wrote:
>>
>>>>
>>>> I recommend, this being the case, to replace 'webkit' with 'experimental'.
2001 Mar 23
3
Login Failure
Greetings. Is there something up with Samba and RedHat,
or with recent kernels, or with some packages that have
been updated recently? A lot of us seem to see the
same login errors with samba and I have yet to get my
windows clients to login to my new samba server. The
log messages really don't help.
I had an old server running Samba 2.0.7 (RedHat 5.0 upgraded
to nearly 5.2 with 2.0.33).
2013 Oct 18
0
[LLVMdev] [RFC] Stackmap and Patchpoint Intrinsic Proposal
On Oct 18, 2013, at 12:39 PM, Chris Lattner <clattner at apple.com> wrote:
> On Oct 18, 2013, at 11:08 AM, Andrew Trick <atrick at apple.com> wrote:
>
>>>
>>> I recommend, this being the case, to replace 'webkit' with 'experimental'. Having webkit in the name implies some dependence on webkit, and there is none. Plus, this functionality will
2013 Oct 18
5
[LLVMdev] [RFC] Stackmap and Patchpoint Intrinsic Proposal
This is a proposal for adding Stackmaps and Patchpoints to LLVM. The
first client of these features is the JavaScript compiler within the
open source WebKit project.
A Stackmap is a record of variable locations (registers and stack
offsets) at a particular instruction address.
A Patchpoint is an instruction address at which space is reserved for
patching a new instruction sequence at runtime.
2014 Aug 05
4
[LLVMdev] LLVM as a shared library
> (7) Make the C API truly great.
>
> I think it’s harmful to LLVM in the long run if external embedders use the C++ API. I think that one way of ensuring that they don’t have an excuse to do it is to flesh out some things:
>
> - Add more tests of the C API to ensure that people don’t break it accidentally and to give more gravitas to the C API backwards compatibility claims.
>