similar to: 1.3.30 build error on Mac OS X with non-Apple GCC

Displaying 20 results from an estimated 500 matches similar to: "1.3.30 build error on Mac OS X with non-Apple GCC"

2002 Dec 26
3
R-1.6.2beta_2002-12-20: build problems (PR#2395)
While builds and validations of R-1.6.2beta_2002-12-20 were successful on several systems, there were a few failures: ------------------------------------------------------------------------ Apple Darwin 6.2 (MacOS 10.2.2) with gcc-3.2.1: gcc -dynamiclib -flat_namespace -undefined suppress -o .libs/libgslcblas.0.0.0.dylib sasum.lo saxpy.lo ... isamax.lo izamax.lo xerbla.lo -lc -install_name
2010 Sep 11
2
Re: Trouble with libgsm on Mac OS X 10.6.2
ralniv wrote: > Below are my instructions for getting a libgsm friendly version of Wine compiled on SnowLeopard. I assume that you already have wine-devel installed and configured to your liking. I also assume that you use MacPorts for package management. > > [1] Uninstall wine-devel > > Code: > sudo port uninstall wine-devel > > > > [2] Edit the portfile for
2006 Apr 13
1
R-latest.tar.gz make error
Hi. (MacOSX 10.4.6) I downloaded R-latest.tar.gz just now from src/base- prerelease on CRAN. "make" gave the following error after an apparently successful ./configure: [snip] util.c: In function 'Rf_type2char': util.c:247: warning: return discards qualifiers from pointer target type gcc -I../../src/extra/zlib -I../../src/extra/bzip2 -I../../src/extra/ pcre
2003 Dec 22
2
R-devel with Darwin: some issues (mostly due to latest R.framework changes)
Some issues with the recent R-devel (rsync today) on Darwin: 1) Recent R-devel is a bit misleading concerning the R-framework installation: A new option --enable-R-framework was introduced, but install-Rframework ignores its absence (or --disable-R-framework for that matter) and tries to install the framework anyway in / which fails just after the R itself was copied into /Versions/.... I
2019 Feb 05
2
[Release-testers] LLVM 7.1.0 release - Please test the branch
On 02/05/2019 11:26 AM, Michał Górny wrote: > On Tue, 2019-02-05 at 11:23 -0800, Tom Stellard wrote: >> On 02/05/2019 08:07 AM, Michał Górny wrote: >>> On Tue, 2019-02-05 at 07:36 -0800, Tom Stellard via Release-testers >>> wrote: >>>> Hi, >>>> >>>> The release_70 branch is ready for the 7.1.0 release. I have updated the
2019 Feb 06
2
[Release-testers] LLVM 7.1.0 release - Please test the branch
On Tue, 2019-02-05 at 16:13 -0800, Tom Stellard wrote: > On 02/05/2019 11:32 AM, Tom Stellard via Release-testers wrote: > > On 02/05/2019 11:26 AM, Michał Górny wrote: > > > On Tue, 2019-02-05 at 11:23 -0800, Tom Stellard wrote: > > > > On 02/05/2019 08:07 AM, Michał Górny wrote: > > > > > On Tue, 2019-02-05 at 07:36 -0800, Tom Stellard via
2019 Feb 07
2
[Release-testers] LLVM 7.1.0 release - Please test the branch
On Wed, 2019-02-06 at 14:09 -0800, Tom Stellard wrote: > On 02/05/2019 10:41 PM, Michał Górny wrote: > > On Tue, 2019-02-05 at 16:13 -0800, Tom Stellard wrote: > > > On 02/05/2019 11:32 AM, Tom Stellard via Release-testers wrote: > > > > On 02/05/2019 11:26 AM, Michał Górny wrote: > > > > > On Tue, 2019-02-05 at 11:23 -0800, Tom Stellard wrote: >
2013 Oct 01
2
Unknown versions in git.
bat guano wrote: >> >> "script failed to extract a version" > > Shouldn't the "update_version" scripts be called during the autogen.sh processes? It's run by configure (look for the CURRENT_VERSION definition).
2010 Oct 30
1
Re: Trouble with libgsm on Mac OS X 10.6.2
Folks, In answer to the error "libgsm 32-bit development files not found," after completing the libtool command, you must copy the library to /usr/lib. "cp lib/* /usr/lib" would do nicely. HTH, David
2010 Jul 14
1
Re: Trouble with libgsm on Mac OS X 10.6.2
Below are my instructions for getting a libgsm friendly version of Wine compiled on SnowLeopard. I assume that you already have wine-devel installed and configured to your liking. I also assume that you use MacPorts for package management. [1] Uninstall wine-devel Code: sudo port uninstall wine-devel [2] Edit the portfile for wine-devel. It is located at:
2019 Feb 05
2
[Release-testers] LLVM 7.1.0 release - Please test the branch
On 02/05/2019 08:07 AM, Michał Górny wrote: > On Tue, 2019-02-05 at 07:36 -0800, Tom Stellard via Release-testers > wrote: >> Hi, >> >> The release_70 branch is ready for the 7.1.0 release. I have updated the >> version and pushed a fix for https://bugs.llvm.org/show_bug.cgi?id=39427, >> which is the only bug we will be fixing in this release. >> >>
2010 Dec 04
2
Re: Trouble with libgsm on Mac OS X 10.6.2
The only way I could get rid of the err for gsm on launch was to copy libgsm to my DDO folder, even those I use DYLD_FALLBACK_LIBRARY_PATH, and libgsm is in all of those locations. Here's my launching script: Code: on run --edit this to be the correct location and file to run (typically only edit after the "drive_c") set toRun to
2004 Nov 08
3
Comments on the R-2.0.0 release (PR#7351)
Builds of the R-2.0.0 release have been considerably more successful at my site than previous releases. I now have it installed on these platforms: Apple PowerPC G3 267MHz GNU/Linux 2.4.19-4a (Yellow Dog Linux release 2.3 (Dayton)) Compaq Alpha Sierra OSF/1 5.1 Compaq/DEC Alpha OSF/1 4.0F Intel Itanium-2 GNU/Linux Red Hat Linux Advanced Server release 2.1AS (Derry) Intel Pentium II FreeBSD
2016 Jan 27
2
Problem with the way BUILD_SHARED_LIBS=ON handled in llvm 3.8
Hi, On Tue, Jan 26, 2016 at 6:57 PM, ChrisBieneman <beanz at apple.com> wrote: > Yes, I'm aware of the change that caused this. It was when I stopped setting SOVERSION as a target property on all shared libraries. That change was deliberate in order to match functionality between CMake and the autoconf build. > > In the autoconf build we didn't actually set the SOVERSION on
2007 Jan 30
1
Error message when building a package
I'm trying to build a package. The machine is PowerPC G4 with Mac OS 10.4.8, and I'm using R2.4.1. I get "R CMD build roots" working, and it created roots.tar.gz. But I get the following message when I run "R CMD INSTALL -l ../myrlibrary roots.tar.gz" ====================================================================== * Installing *source* package 'roots'
2009 Aug 05
2
FLAC 1.2.1 on OS X 10.4.11
hi, according to the FAQ flac supports multichannel formats. i had no luck with 1.1.4 though ( "Untitled.aif: ERROR: unsupported number channels 8 for AIFF" ), i guess that feature was added in 1.2? unfortunately, the binary for 1.2 does not run on OS X 10.4 (says libiconv is too old). i removed libiconv and reinstalled that from source, but then flac 1.2.1 just prints
2020 May 21
5
Understanding the version handling in LLVM/Clang/LLD
[ Please CC me I ma not subcribed to this mailing-list ] [ CC Tom and Hans as LLVM/stable maintainers ] Hi, I want to understand the version handling in LLVM/Clang/LLD. Normally, I build from "release/10.x" Git branch by using the tool tc-build from ClangBuiltLinux project. With "llvm-10.0.1-rc1" Git tag I was able to setup a llvm-toolchain consisting of the projects
2006 Jun 02
1
Installation R-2.3.1 on IBM AIX5.3 (PR#8931)
Full_Name: Karsten Tabelow Version: R-2.3.1 OS: AIX5.3 Submission from: (NULL) (62.141.176.2) Specification in config.site: CC=xlc_r CFLAGS='-O -qstrict' F77=xlf_r FFLAGS='-O -qstrict' SHLIB_LDFLAGS='-G' DYLIB_LDFLAGS='-G' LDFLAGS='-brtl' CXX=xlc++_r CXXFLAGS='-O -qstrict' Complilation error in src/main/printutils.c: "printutils.c",
2007 Jun 04
2
[LLVMdev] building llvm-gcc4 with a different target name
Hello, I've put together a macports version of llvm and llvm-gcc4, but I've run into a problem with how gcc on the mac works. llvm-gcc4 creates an executable named: /opt/local/bin/powerpc-apple-darwin8-gcc-4.0.1 Which happens to be the same executable in /usr/bin. Because I have /opt/local before /usr/bin, gcc ends up using llvm-gcc4 to build all my code. Most of the time this
2006 Nov 22
1
Help with Multiple Readers, 1 Writer scenario
Some time back in September, [sorry to be so slow], Dave wrote: > When you open an IndexReader on the index it is opened up on > that particular version (or state) of the index. So any > operations on the IndexReader (like searches) will only show > what was in the index at the time you opened it. Any modifications > to the index (usually through and IndexWriter) that occur