Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] llvm-gcc and -march"
2011 Aug 22
2
[LLVMdev] llvm-gcc and -march
This comes up when trying to compile Valgrind, here is the full compile line:
/opt/local/bin/llvm-gcc-4.2 -Wbad-function-cast -Wcast-qual
-Wcast-align -fstrict-aliasing \
-arch x86_64 -O2 -g -Wall -Wmissing-prototypes -Wshadow
-Wpointer-arith -Wstrict-prototypes -Wmissing-declarations
-Wno-format-zero-length -fno-strict-aliasing -mmacosx-version-min=10.5
-fno-stack-protector \
-O -S
2011 Aug 22
2
[LLVMdev] llvm-gcc and -march
Here is some more info:
[naromero:~/pmr] naromero% llvm-gcc -v
Using built-in specs.
Target: x86_64-apple-darwin10
Configured with: ../llvm-gcc-4.2-2.9.source/configure
--prefix=/opt/local --host=x86_64-apple-darwin10
--enable-llvm=/opt/local --enable-languages=c,c++,objc,obj-c++,fortran
--libdir=/opt/local/lib/llvm-gcc42
--includedir=/opt/local/include/llvm-gcc42
--infodir=/opt/local/share/info
2011 Aug 22
0
[LLVMdev] llvm-gcc and -march
Still nothing here:
[yendi:~] echristo% llvm-gcc -march=nocona foo.c -S -arch x86_64
[yendi:~] echristo%
So, perhaps you could send more information? Or bug the mac ports people.
-eric
On Aug 22, 2011, at 2:44 PM, Nichols A. Romero wrote:
> This comes up when trying to compile Valgrind, here is the full compile line:
>
> /opt/local/bin/llvm-gcc-4.2 -Wbad-function-cast -Wcast-qual
2011 Aug 22
0
[LLVMdev] llvm-gcc and -march
The -arch option is handled by Apple's "driver-driver", and the MacPorts build is probably not using that. See the driverdriver.c source file in llvm-gcc for details.
On Aug 22, 2011, at 3:08 PM, Nichols A. Romero wrote:
> Here is some more info:
>
> [naromero:~/pmr] naromero% llvm-gcc -v
> Using built-in specs.
> Target: x86_64-apple-darwin10
> Configured with:
2011 Aug 22
2
[LLVMdev] llvm-gcc and -march
On Aug 22, 2011, at 3:59 PM, Bob Wilson wrote:
> The -arch option is handled by Apple's "driver-driver", and the MacPorts build is probably not using that. See the driverdriver.c source file in llvm-gcc for details.
>
He's asking about the -march option which should work either way.
Also, the driver-driver should be in the sources that they're using even still.
2011 Aug 22
0
[LLVMdev] llvm-gcc and -march
On Mon, Aug 22, 2011 at 2:34 PM, Nichols A. Romero <naromero at gmail.com> wrote:
> Hi,
>
> I apologize if I am not asking on the right mailing list.
>
> I am using the llvm-gcc4.2 from MacPorts.
> https://trac.macports.org/browser/trunk/dports/lang/llvm-gcc42/Portfile
>
> llvm-gcc does not seem to accept the -march flag. This is the error,
> I got:
>
> cc1:
2011 Aug 22
0
[LLVMdev] llvm-gcc and -march
So my original post subject was for -march, but that was my mistake.
The command line option
is -arch.
Since presumably Macports is just fetching an llvm tar ball from some
repository, is the issue that llvm
has been misconfigure in some obvious way? Yes, I can take a look at
the driverdriver.c source file
as well.
Should this also be working in LLVM 2.9 or is the latest SVN also needed?
On
2014 Nov 20
2
building NUT on Mac OS X Yosemite
Hello,
Here is a summary of discussions around NUT builds on Mac OS X 10.10.
Starting from https://github.com/networkupstools/nut-website/issues/7 <https://github.com/networkupstools/nut-website/issues/7>
@JeanPerriault
I've found msort on macports (https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile, http://billposer.org/Software/Downloads/
msort.pdf), but I'm
2014 Nov 20
0
building NUT on Mac OS X Yosemite (website/documentation)
On Nov 20, 2014, at 7:11 AM, Jean Perriault (GM TAF) <jpweb.taf at gmail.com> wrote:
> Hello,
> Here is a summary of discussions around NUT builds on Mac OS X 10.10.
>
> Starting from https://github.com/networkupstools/nut-website/issues/7
>
> @JeanPerriault
> I've found msort on macports (https://trac.macports.org/browser/trunk/dports/textproc/msort/Portfile,
2008 Jan 23
3
Rsync 3.0.0pre8 and Mac OS X
Hi,
I tried Rsync 3.0.0pre8 on my mac running os X 10.5.
I was very pleased about the --iconv feature, as i have to sync some
LINUX-machines and I had really trouble with some filenames.
But I found one strange thing in connection with the mac.
First of all, the translation between the LINUX ISO-8859-15 and the
mac ut-8 works (nearly) perfect.
As I live in Germany, we have often filenames
2009 Jun 10
1
[expect deadlock] on MAC OS X
after my success in getting some proprietary company software working in wine clicky (http://forum.winehq.org/viewtopic.php?p=25947#25947)
one of my colleagues is attempting the install on MAC OS X
they have installed wine using this guide http://davidbaumgold.com/tutorials/wine-mac/ (http://davidbaumgold.com/tutorials/wine-mac/)
1. to install winetricks can they issue?
Code:
wget
2010 Jul 12
13
16-Bit/DOS Suppor Missing?
Currently attempting to run an old PC game on my Mac (Leopard). I've installed Wine using MacPorts, which worked flawlessly. Now when I attempt to install my PC Game the terminal responds with "16-Bit/DOS Support missing."
Is there a way to fix this?
2008 Feb 06
2
[LLVMdev] strange visibility error when compiling llvm-gcc-4.2
I'm on Debian Etch and re-compile llvm/llvm-gcc-4.2 from
scratch. I'm on svn revision 46813.
I'm using the following commands for the compilation:
----------------------------------
# Get the sources
mkdir /s/llvm
cd /s/llvm
svn co http://llvm.org/svn/llvm-project/llvm/trunk /s/llvm/svn.llvm
svn co http://llvm.org/svn/llvm-project/llvm-gcc-4.2/trunk /s/llvm/svn.gcc42
# Compile llvm
2008 Aug 11
0
[LLVMdev] gfortran link failure in current llvm svn
Hi,
> I am confused. Shouldn't the gcc 4.2 front-end build behave
> just like the FSF gcc build. The first stage builds the compilers
> and the second stage rebuilds them using those from the first
> stage?
the FSF gcc requires you to build the C compiler (I think - will check).
Thus a newly built C compiler is always available to build later stages.
We can't reasonably
2008 Aug 11
5
[LLVMdev] gfortran link failure in current llvm svn
The curent llvm svn (r54623) is unable to link the gfortran
compiler in llvm-gcc-4.2 svn. I am getting the error...
c++ -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -mdynamic-no-pic -DHAVE_CONFIG_H -o f951 \
2008 Feb 06
0
[LLVMdev] strange visibility error when compiling llvm-gcc-4.2
Hi,
> if /bin/sh ./libtool --mode=compile /s/llvm/obj.gcc42/./gcc/xgcc -B/s/llvm/obj.gcc42/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/local/i686-pc-linux-gnu/lib/ -isystem /usr/local/i686-pc-linux-gnu/include -isystem /usr/local/i686-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/s/llvm/svn.gcc42/libgomp -I. -I/s/llvm/svn.gcc42/libgomp/config/linux/x86
2008 Aug 11
2
[LLVMdev] gfortran link failure in current llvm svn
Duncan,
I am confused. Shouldn't the gcc 4.2 front-end build behave
just like the FSF gcc build. The first stage builds the compilers
and the second stage rebuilds them using those from the first
stage?
Jack
On Mon, Aug 11, 2008 at 03:56:23PM +0200, Duncan Sands wrote:
> > I don't be that can be the cause because I have...
> >
> >
2008 Feb 06
6
[LLVMdev] strange visibility error when compiling llvm-gcc-4.2
On Feb 6, 2008, at 5:18 AM, Duncan Sands wrote:
> Hi,
>
>> if /bin/sh ./libtool --mode=compile /s/llvm/obj.gcc42/./gcc/xgcc -B/
>> s/llvm/obj.gcc42/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/
>> local/i686-pc-linux-gnu/lib/ -isystem /usr/local/i686-pc-linux-gnu/
>> include -isystem /usr/local/i686-pc-linux-gnu/sys-include -
>> DHAVE_CONFIG_H -I.
2014 Nov 23
0
building NUT on Mac OS X Yosemite (website/documentation)
Sorry I ran ?make' command in nut-website/nut... (I still can?t understand why creating man page is so long, it is much more faster on ubuntu.)
When running ?make? in nut-website, same issue then described previously, even with Arno patch
> sort: stray character in field spec: invalid field specification `4.1,4.5rV
>
> >>>>>> and it ends with:
>
>
2014 Nov 23
6
building NUT on Mac OS X Yosemite (website/documentation)
After a fresh ?nut' (version 2.7.2.5) clone on Yosemite,
Configuration summary:
======================
build serial drivers: yes
build USB drivers: yes
build SNMP drivers: yes
build neon based XML driver: yes
enable Avahi support: no
build Powerman PDU client driver: no
build IPMI driver: no
build Mac OS X meta-driver: yes
build i2c based drivers: no
enable SSL support: yes (OpenSSL)