Re: gcc & libgcc 6/7/8

Back on-list again: As noted by Ryan, GCC6 and prior use libgcc from GCC6. There is(are) ABI change(s) in libgcc from GCC6 to GCC7 (e.g., some different compatibility versions for libraries; some different symbols in libraries; some different version in filenames). I don't know about GCC8 yet. Thu

Re: gcc & libgcc 6/7/8

Hi all, Is there some reason that the libgcc ports are not named liked the gcc ports? In particular, shouldn't there be a libgcc6, libgcc7 and a new libgcc8 port? Cheers! Frank > On Jun 30, 2017, at 8:08 AM, Michael Dickens wrote: > > Back on-list again: > > As noted by Ryan, GCC6 and pri

Re: gcc & libgcc 6/7/8

I'm new to the *GCC* ports, so I don't know why libgcc# is not matched with gcc#. Seems like it would be possible to install libgcc# into $prefix/lib/libgcc#/ , so that one could have all of the various gcc#'s installed at the same time without conflicting. But, then I've never tried & this certain

Re: port install pear-TCPDF fails with checksum error

any developer out there who can help me with PCTDF ? > On 28 Jun 2017, at 05:27, Joshua Root wrote: > > On 2017-6-28 09:29 , macpo...@parvis.nl wrote: >>> On 27 Jun 2017, at 07:42, Joshua Root wrote: >>> >>> Generally you should look at the contents of the HTML fil

Re: gcc & libgcc 6/7/8

On 2017-06-30 16:24, m...@macports.org wrote: > Is there some reason that the libgcc ports are not named liked the > gcc ports? The reason for libgcc is that all gcc versions are supposed to link to the same runtime libraries. Reverting this would probably bring back the old bugs. https://lists.m

Re: gcc & libgcc 6/7/8

I think that's it. libgcc @6.x can service all the gccs from about 4.7 to 6.x, so there is only one. Too bad we need a new version for gcc7. More complexity, more complications. But that's progress. Hopefully the broken gcc7 build on older systems can be remedied. Ken On 2017-06-30, at 7:33

Re: running clang compiler test suite from within macports infrastructure?

Thanks, Jack. There appear to be different ways to test clang. I thought the testing would all happen in during or related to the build, but this does not appear to be exactly so. At any rate, there is a "test-suite" of 400+ tests for each version of clang, which is one way to test it. It is u

Re: port install pear-TCPDF fails with checksum error

Try this Portfile and tell me if it works for you. Regards, Bradley Giesbrecht (pixilla) Portfile Description: Binary data > On Jun 30, 2017, at 7:42 AM, macpo...@parvis.nl wrote: > > any developer out there who can help me with PCTDF ? > > >> On 28 Jun 2017, at 05:27, Joshua Root wrote

Trac requires GitHub account

I just noticed that trac requires a GitHub account to create ticket. Do we have a recommended way for people without GitHub accounts to report issues other then the mailing list? Regards, Bradley Giesbrecht (pixilla)

Travis: failed build reported as successful

Dear Zero King, Why is this build reported as successful? https://travis-ci.org/macports/macports-ports/jobs/248896726 Also: can it be that we're experiencing troubles due to an unusual $HOME variable? Mojca

Re: Travis: failed build reported as successful

On Fri, Jun 30, 2017 at 10:51:54PM +0200, Mojca Miklavec wrote: Dear Zero King, Why is this build reported as successful? https://travis-ci.org/macports/macports-ports/jobs/248896726 1. Lint error was ignored. I didn't fix it because "file delete -force" errors aren't fixed. 2. `portindex` f

Re: running clang compiler test suite from within macports infrastructure?

This test suite proved very very helpful! Clang-3.8 on PPC produced only 13 errors out of 500 tests. 10 of those were on the same issue, 32bit exceptions. The other three included on a weird math error in fast-fourier-transfroms, and two errors in the logic of handling certain va_args (which I

Re: Trac requires GitHub account

On 2017-7-1 02:28 , Bradley Giesbrecht wrote: I just noticed that trac requires a GitHub account to create ticket. Do we have a recommended way for people without GitHub accounts to report issues other then the mailing list? No. Is creating a GitHub account a problem for someone? - Josh

Re: Travis: failed build reported as successful

On 1 July 2017 at 04:33, Zero King wrote: > On Fri, Jun 30, 2017 at 10:51:54PM +0200, Mojca Miklavec wrote: >> >> Dear Zero King, >> >> Why is this build reported as successful? >> >> https://travis-ci.org/macports/macports-ports/jobs/248896726 > > 1. Lint error was ignored. I didn't fix it because

Travis: list of installed files

Hi, When looking at some pull requests which built successfully I realized that I would want to check the list of installed files. Now, we could either add that list to other logs, but I expect that for nearly all ports the list of installed files could probably be displayed at the end of the reg