On 2017-11-07, at 2:20 PM, Joshua Root wrote:
>
>
> Looks more like it was made to support programs using gnulib, which
> apparently provides its own setlocale implementation. I would probably
> have tried including the gettext header last before undefining the macro.
>
> The intent of having t
Hi,
A while ago I packaged MinGW's gcc and left out one optional step, but
I need that one now.
The procedure is as follows:
(a) install a bunch of dependencies
(b) compile gcc to phase 1 (I currently call that port
i686-w64-mingw32-gcc-bootstrap)
(c) install some more files (i686-w64-mingw32-
On 2017-11-8 05:46 , Ken Cunningham wrote:
>
> that definition is guarded by a flag
>
> #ifndef GNULIB_defined_setlocale /* don't override gnulib */
> #undef setlocale
> #define setlocale libintl_setlocale
> extern char *setlocale (int, const char *);
> #endif
>
>
> and sure enough, adding this
On 2017-11-07 19:46, Ken Cunningham wrote:
and sure enough, adding this to the portfile fixes the build:
configure.cxxflags-append -DGNULIB_defined_setlocale
I presume this workaround was made for this very error.
I have pushed the fix in commit 915114f:
https://github.com/macports/macports-p
On 2017-11-07 20:21, Ryan Schmidt wrote:
On Nov 7, 2017, at 13:19, Leonardo Brondani Schenkel wrote:
The plot thickens. I cannot even compile a small test program:
$ cat test.cpp
#include
int main() {
std::cout << "Hello world";
return 0;
}
$ clang-mp-5.0 test.cpp
ld: unexpe
On Nov 7, 2017, at 13:19, Leonardo Brondani Schenkel wrote:
> The plot thickens. I cannot even compile a small test program:
>
> $ cat test.cpp
> #include
>
> int main() {
>std::cout << "Hello world";
>return 0;
> }
>
> $ clang-mp-5.0 test.cpp
> ld: unexpected token: !tapi-tbd
The plot thickens. I cannot even compile a small test program:
$ cat test.cpp
#include
int main() {
std::cout << "Hello world";
return 0;
}
$ clang-mp-5.0 test.cpp
ld: unexpected token: !tapi-tbd-v2 file
'/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Dev
>
> Unfortunately that did not work for me, the port fails at the configure phase:
>
> -- The C compiler identification is Clang 5.0.0
> -- The CXX compiler identification is Clang 5.0.0
> -- Check for working C compiler: /opt/local/bin/clang-mp-5.0
> -- Check for working C compiler: /opt/local/b
On 2017-11-07 19:46, Ken Cunningham wrote:
Leonardo, I find you can reproduce this build error on any system (I
just did it on high sierra) if you do this:
install clang-5.0 and libgcc as normally from the prebuilt packages
sudo port install libgcc clang-5.0
then run
sudo port -v -s destroot
On Nov 7, 2017, at 06:07, Michael Dickens wrote:
> Reverted in <
> https://github.com/macports/macports-ports/commit/44373e0fd9955702e9e2f6820b2cf595fec24c65
>> . Thanks for testing & feedback.
Thank you!
> If/when the release is moved to
> requiring C++11, I'll also create a subport for the la
On 2017-11-07, at 2:13 AM, Joshua Root wrote:
>
>
> There is an indirect dependency via glib2. The issue really is the macro
> in the gettext header causing unintended changes to the C++ headers.
>
> - Josh
totally get it now. It builds easily with libc++, but fails with libstdc++ or
macport
We have a port for meson, a new build system.
The libhttpseverywhere portfile uses it, and contains a lot of code for dealing
with it.
Should we have a meson portgroup to abstract away these details? Has anyone
worked on that already?
I want to investigate using meson for glib2 but I don't wan
Hi,
This is a reminder about one burning issue.
I'm currently trying to build wine and I don't see any way to avoid
building gtk3 from sources (gtk3 seems to build forever). Also, I
would like to have gtk3 +quartz build anyway which means compiling
from source on a no-matter-what basis.
Could we
Reverted in <
https://github.com/macports/macports-ports/commit/44373e0fd9955702e9e2f6820b2cf595fec24c65
>. Thanks for testing & feedback. If/when the release is moved to
requiring C++11, I'll also create a subport for the last version that
doesn't, for bootstrap purposes per our discussion (assumi
On 2017-11-7 19:27 , Ken Cunningham wrote:
>
> So my usual machine is 10.6.8, set up with LibcxxOnOlderSystems, and default
> compiler is presently clang-3.9.
>
> With that, it built straight through without any trouble:
>
> $ port -v installed xdxf_makedict
> The following ports are currently
On 2017-11-7 19:35 , Ken Cunningham wrote:
>
> On 2017-11-07, at 12:30 AM, Ken Cunningham wrote:
>>
>>
>>>
>>> -- Found libintl: /opt/local/lib/libintl.dylib
>
>
> my error - blurry eyes.
>
> like josh said, this is provided by gettext.
>
> perhaps gettext is the real missing dep.
There is a
On 2017-11-07, at 12:30 AM, Ken Cunningham wrote:
>
>
>>
>> -- Found libintl: /opt/local/lib/libintl.dylib
my error - blurry eyes.
like josh said, this is provided by gettext.
perhaps gettext is the real missing dep.
On 2017-11-07, at 12:27 AM, Ken Cunningham wrote:
>
> -- Found libintl: /opt/local/lib/libintl.dylib
>
> so perhaps there is a missing dep for port:libiconv
>
> Ken
>
>
No, seems you have that dep there. Maybe it's the newer compiler...
I'll include the whole build log for you to see, em
On 2017-11-07, at 12:03 AM, Ken Cunningham wrote:
>
> On 2017-11-06, at 11:35 PM, Leonardo Brondani Schenkel wrote:
>
>> Hello all,
>>
>> I recently introduced a new port, xdxf_makedict, which built successfully on
>> my box (macOS 10.13) on first try. However, after it got merged I started
On 2017-11-7 18:35 , Leonardo Brondani Schenkel wrote:
> - 10.8:
> https://build.macports.org/builders/ports-10.8_x86_64_legacy-builder/builds/42330/steps/install-port/logs/stdio
>
> - 10.7: same problem as 10.8
> - 10.6:
> https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/build
On 2017-11-06, at 11:35 PM, Leonardo Brondani Schenkel wrote:
> Hello all,
>
> I recently introduced a new port, xdxf_makedict, which built successfully on
> my box (macOS 10.13) on first try. However, after it got merged I started
> getting notifications from the buildbots about build failure
21 matches
Mail list logo
