Displaying 20 results from an estimated 21 matches for "crtbegint".
Did you mean:
crtbegin
2007 Jan 10
4
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
...BGCC2_CFLAGS="-O2 -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem
./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED " \
MULTILIB_CFLAGS="" T= crtbegin.o crtend.o crtbeginS.o crtendS.o
crtbeginT.o
make[3]: Entering directory `/home/xzx/llvm-gcc-obj/gcc'
make[3]: `crtbegin.o' is up to date.
make[3]: `crtend.o' is up to date.
make[3]: `crtbeginS.o' is up to date.
make[3]: `crtendS.o' is up to date.
make[3]: `crtbeginT.o' is up to date.
make[3]: Leaving directory `/hom...
2007 Jan 10
0
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
...GCC -W -Wall -Wwrite-strings
> -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
> -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
> -D__GCC_FLOAT_NOT_NEEDED " \
> MULTILIB_CFLAGS="" T= crtbegin.o crtend.o crtbeginS.o crtendS.o
> crtbeginT.o
> make[3]: Entering directory `/home/xzx/llvm-gcc-obj/gcc'
> make[3]: `crtbegin.o' is up to date.
> make[3]: `crtend.o' is up to date.
> make[3]: `crtbeginS.o' is up to date.
> make[3]: `crtendS.o' is up to date.
> make[3]: `crtbeginT.o' is up to date.
&g...
2007 Jan 11
2
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
...-Wwrite-strings
>> -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
>> -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
>> -D__GCC_FLOAT_NOT_NEEDED " \
>> MULTILIB_CFLAGS="" T= crtbegin.o crtend.o crtbeginS.o crtendS.o
>> crtbeginT.o
>> make[3]: Entering directory `/home/xzx/llvm-gcc-obj/gcc'
>> make[3]: `crtbegin.o' is up to date.
>> make[3]: `crtend.o' is up to date.
>> make[3]: `crtbeginS.o' is up to date.
>> make[3]: `crtendS.o' is up to date.
>> make[3]: `crtbeginT....
2007 Jan 12
2
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
...rototypes -Wmissing-prototypes -Wold-style-definition
> >>> -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
> >>> -D__GCC_FLOAT_NOT_NEEDED " \
> >>> MULTILIB_CFLAGS="" T= crtbegin.o crtend.o crtbeginS.o crtendS.o
> >>> crtbeginT.o
> >>> make[3]: Entering directory `/home/xzx/llvm-gcc-obj/gcc'
> >>> make[3]: `crtbegin.o' is up to date.
> >>> make[3]: `crtend.o' is up to date.
> >>> make[3]: `crtbeginS.o' is up to date.
> >>> make[3]: `crtendS.o'...
2007 Jan 11
0
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
...;>> -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
>>> -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
>>> -D__GCC_FLOAT_NOT_NEEDED " \
>>> MULTILIB_CFLAGS="" T= crtbegin.o crtend.o crtbeginS.o crtendS.o
>>> crtbeginT.o
>>> make[3]: Entering directory `/home/xzx/llvm-gcc-obj/gcc'
>>> make[3]: `crtbegin.o' is up to date.
>>> make[3]: `crtend.o' is up to date.
>>> make[3]: `crtbeginS.o' is up to date.
>>> make[3]: `crtendS.o' is up to date.
>>&...
2010 Mar 25
1
Static linking
...is described in https://issues.asterisk.org/view.php?id=15915. According to the last post in the bug report, a workaround is using of static linking. When I tried (I
enabled option Compiler Flags/STATIC_BUILD) it I got the following error message:
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.1.2/crtbeginT.o: relocation R_X86_64_32 against `__deregister_frame_info' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-linux-gnu/4.1.2/crtbeginT.o: could not read symbols: Bad value
I tried to compile Asterisk 1.6.1.17 on Debian/etch/x86_64 with gcc-4.1.2 and gcc-3.4...
2007 Jan 12
0
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
...ing-prototypes -Wold-style-definition
> >>> -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
> >>> -D__GCC_FLOAT_NOT_NEEDED " \
> >>> MULTILIB_CFLAGS="" T= crtbegin.o crtend.o crtbeginS.o crtendS.o
> >>> crtbeginT.o
> >>> make[3]: Entering directory `/home/xzx/llvm-gcc-obj/gcc'
> >>> make[3]: `crtbegin.o' is up to date.
> >>> make[3]: `crtend.o' is up to date.
> >>> make[3]: `crtbeginS.o' is up to date.
> >>> make...
2006 Mar 07
0
[LLVMdev] Re: Re: Re: New GCC4-based C/C++/ObjC front-end for LLVM
.../libcpp/include
-I/space/p2/ghost/build/llvm-cvs/include -g0 -finhibit-size-directive
-fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss
-fno-unit-at-a-time -fno-omit-frame-pointer \
-c ../../2006-03-02-llvm-gcc-4/gcc/crtstuff.c -DCRT_BEGIN
-DCRTSTUFFT_O \
-o crtbeginT.o
In file included from ../../2006-03-02-llvm-gcc-4/gcc/crtstuff.c:67:
../../2006-03-02-llvm-gcc-4/gcc/unwind-dw2-fde.h: In function 'get_cie':
../../2006-03-02-llvm-gcc-4/gcc/unwind-dw2-fde.h:163: warning: return from
incompatible pointer type
Invalid operand found in inline asm: 'call...
2014 Feb 07
2
[Announcement] Tinc version 1.1pre10 released
With pleasure we announce the release of tinc version 1.1pre10. Here is a
summary of the changes:
* Added a benchmark tool (sptps_speed) for the new protocol.
* Fixed a crash when using Name = $HOST while $HOST is not set.
* Use AES-256-GCM for the new protocol.
* Updated support for Solaris.
* Allow running tincd without a private ECDSA key present when
ExperimentalProtocol is not
2014 Feb 07
2
[Announcement] Tinc version 1.1pre10 released
With pleasure we announce the release of tinc version 1.1pre10. Here is a
summary of the changes:
* Added a benchmark tool (sptps_speed) for the new protocol.
* Fixed a crash when using Name = $HOST while $HOST is not set.
* Use AES-256-GCM for the new protocol.
* Updated support for Solaris.
* Allow running tincd without a private ECDSA key present when
ExperimentalProtocol is not
2008 Mar 24
0
[LLVMdev] Potential breakage in llvm-gcc's ./configure
...gcc/../include
> -I/home/jo/llvm-gcc-src/gcc/../libcpp/include -g0
> -finhibit-size-directive -fno-inline-functions -fno-exceptions
> -fno-zero-initialized-in-bss -fno-unit-at-a-time -fno-omit-frame-pointer
> -c /home/jo/llvm-gcc-src/gcc/crtstuff.c -DCRT_BEGIN -DCRTSTUFFT_O
> -o crtbeginT.o
>
> (slightly edited to leave out multiple blanks and line continuation
> backslashes).
>
> The error messages are just what I had seen earlier:
>
> /tmp/ccVjR8Qt.s: Assembler messages:
> /tmp/ccVjR8Qt.s:33: Error: suffix or operands invalid for `push'
> /tmp/...
2008 Mar 24
7
[LLVMdev] Potential breakage in llvm-gcc's ./configure
...gcc/.
-I/home/jo/llvm-gcc-src/gcc/../include
-I/home/jo/llvm-gcc-src/gcc/../libcpp/include -g0
-finhibit-size-directive -fno-inline-functions -fno-exceptions
-fno-zero-initialized-in-bss -fno-unit-at-a-time -fno-omit-frame-pointer
-c /home/jo/llvm-gcc-src/gcc/crtstuff.c -DCRT_BEGIN -DCRTSTUFFT_O
-o crtbeginT.o
(slightly edited to leave out multiple blanks and line continuation
backslashes).
The error messages are just what I had seen earlier:
/tmp/ccVjR8Qt.s: Assembler messages:
/tmp/ccVjR8Qt.s:33: Error: suffix or operands invalid for `push'
/tmp/ccVjR8Qt.s:43: Error: suffix or operands invalid...
2005 Jun 13
2
[LLVMdev] problem compiling the cfrontend on Linux/PPC
...it the file llvm-gcc/gcc/config/rs6000/t-ppccomm and remove some
targets from the variable EXTRA_MULTILIB_PARTS (bug stop after bug stop)
:
-------------------------------------------------------------
EXTRA_MULTILIB_PARTS = crtbegin$(objext) crtend$(objext) \
crtbeginS$(objext) crtendS$(objext) crtbeginT$(objext)
-------------------------------------------------------------
Now, it stoppes there:
gmake[1]: Entering directory
`/usr/local/home/cyrille/project/llvm/cfrontend/build/powerpc-unknown-linux-gnu/libiberty'
if [ x"" != x ] && [ ! -d pic ]; then \
mkdir pic; \
else...
2006 Mar 02
4
[LLVMdev] Re: Re: New GCC4-based C/C++/ObjC front-end for LLVM
On Thu, 2 Mar 2006, Vladimir Prus wrote:
>>> The instructions seem to have one path wrong. It says to get:
>>
>> I'll put together a tarball today. That will be easier than dealing with
>> a patch, and it will include a bunch of bugfixes since the previous email.
> Further into process, I get this error:
> In file included from
2008 Mar 23
0
[LLVMdev] Potential breakage in llvm-gcc's ./configure
...gcc/.
-I/home/jo/llvm-gcc-src/gcc/../include
-I/home/jo/llvm-gcc-src/gcc/../libcpp/include -g0
-finhibit-size-directive -fno-inline-functions -fno-exceptions
-fno-zero-initialized-in-bss -fno-unit-at-a-time -fno-omit-frame-pointer
-c /home/jo/llvm-gcc-src/gcc/crtstuff.c -DCRT_BEGIN -DCRTSTUFFT_O
-o crtbeginT.o
(slightly edited to leave out multiple blanks and line continuation
backslashes).
The error messages are just what I had seen earlier:
/tmp/ccVjR8Qt.s: Assembler messages:
/tmp/ccVjR8Qt.s:33: Error: suffix or operands invalid for `push'
/tmp/ccVjR8Qt.s:43: Error: suffix or operands invalid...
2005 Jun 13
0
[LLVMdev] problem compiling the cfrontend on Linux/PPC
Cyrille Mescam wrote:
> On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote:
>
>>Cyrille Mescam wrote:
>>
[snip]
>
> In fact, i am using the CFE build procedures. I am on instructions 5.
>
> cyrille
>
Okay, I took a closer look at your output.
I was correct in that gccas is attempting to assemble a native PPC
assembly language file. However,
2005 Jun 13
2
[LLVMdev] problem compiling the cfrontend on Linux/PPC
On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote:
> Cyrille Mescam wrote:
> >Hi,
> >
> >
> >When compiling the cfrontend for Linux/PPC architecture on a powermac
> >G5, i got
> >the following error :
>
> I hate to ask a silly question, but are you using "make bootstrap" to
> build the cfrontend? Your output looks like gccas
2008 Mar 05
0
Press delete key three times in R-2.6.1 to get segmentation fault (PR#10892)
...ynamic}
*link_gomp:
*libgcc:
%{static|static-libgcc:-lgcc
-lgcc_eh}%{!static:%{!static-libgcc:%{!shared-libgcc:-lgcc --as-needed -lgcc_s
--no-as-needed}%{shared-libgcc:-lgcc_s%{!shared: -lgcc}}}}
*startfile:
%{!shared: %{pg|p|profile:gcrt1.o%s;pie:Scrt1.o%s;:crt1.o%s}} crti.o%s
%{static:crtbeginT.o%s;shared|pie:crtbeginS.o%s;:crtbegin.o%s}
*switches_need_spaces:
*cross_compile:
0
*version:
4.2.2
*multilib:
. ;
*multilib_defaults:
*multilib_extra:
*multilib_matches:
*multilib_exclusions:
*multilib_options:
*linker:
collect2
*link_libgcc:
%D
*md_exec_prefix:...
2012 Jul 11
0
[LLVMdev] Compiling llvm and Clang on Linux
It's undocumented FAQ, if you are using RHEL5 (or clone).
- install gcc44-c++
- Build with CC=gcc44 CXX=g++44
- You may need "CC=clang -std=gnu89" to use clang with its glibc.
Have fun!
ps. AFAIK, clang can be built more easily on centos6.
...Takumi
2012/7/11 Sitvanit Ruah <RUAH at il.ibm.com>:
>
> Hello all,
> I am new to this mailing list so I hope this is
2012 Jul 12
3
[LLVMdev] Compiling llvm and Clang on Linux
...itvanit
/usr/bin/gcc44
/usr/bin/gcov44
/usr/bin/i386-redhat-linux6E-gcc44
/usr/lib/gcc
/usr/lib/gcc/i386-redhat-linux6E
/usr/lib/gcc/i386-redhat-linux6E/4.4.6
/usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtbegin.o
/usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtbeginS.o
/usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtbeginT.o
/usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtend.o
/usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtendS.o
/usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtfastmath.o
/usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtprec32.o
/usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtprec64.o
/usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtpre...