Hello everyone!
I am working on a new port, M2VDownzsizer, which is a sister port to the recent
existing port, M2VRequantiser. Both ports are command line programs that
shrink MPEG-2 video and are commonly used when shrinking a DVD-9 video disc to
fit onto a much more affordable DVD-5 writabl
om: Joshua Root
Sent: July 31, 2022 9:38 PM
To: Robert Kennedy
Cc: MacPorts Development
Subject: Re: Help with New Port - M2VDownsizer
On 2022-8-1 10:11 , Robert Kennedy wrote:
> Hello everyone!
>
> I am working on a new port, M2VDownzsizer, which is a sister port to the
> recent exis
added the following to the Makefile:
CFLAGS += -Xarch_ppc64 -faltivec
Thanks again,
Rob
From: macports-dev on behalf of
Robert Kennedy
Sent: July 31, 2022 10:16 PM
To: Joshua Root
Cc: MacPorts Development
Subject: Re: Help with New Port - M2VDownsizer
Thanks
Mark,
I agree with Josh, these headers look like they were automatically generated
using something like "make depends".
When creating a Makefile, it is GOOD practice to include these lines as it will
ensure that the Project will rebuild the correct files when a header file was
changed. Since
ct and making a binary package. (i.e. package management)
If you are still having problems, please EMAIL me the Makefile and I will take
a look.
RobK88
From: macports-dev on behalf of
Robert Kennedy
Sent: August 2, 2022 8:10 AM
To: Mark Brethen ; MacPorts Dev
00 PM
To: Robert Kennedy
Cc: MacPorts Developers
Subject: Re: include files for cgxCADTools
I stripped those lines but there were some glitches in the build. First the
Makefile only defines CC but the source is c++.
:info:build /opt/local/include/opencascade/Standard_Handle.hxx:75:19: wa
Last Friday, I submitted a Pull Request for the abandoned port unalz.
See
https://github.com/macports/macports-ports/pull/15527
The Macport Githib page no longer lists the PR on the list of Pull Requests at
macports Github page. And I no longer see it at my GitHib page RobK88.
Yet the PR is st
I found PR 15527 for unalz on the GitHub page for macports. But I find it
strange that the PR does not appears on my Github page for my unalz branch.
Rob
From: Robert Kennedy
Sent: August 3, 2022 5:14 PM
To: macports-dev@lists.macports.org
Subject: Port unalz
I am working on creating a new port that uses its own config.h. See attached.
The project compiles and builds just in clang outside of Macports but when it
is built via Macports, a number of macro redefined warnings are generated:
e.g.
./config.h:29:9: warning: 'HAVE_STDINT_H' macro redefined
rom: Ryan Schmidt
Sent: August 5, 2022 4:38 PM
To: Robert Kennedy
Cc: MacPorts Developers
Subject: Re: Issues with config.h
Early in config.h it says:
#ifndef LINUX
#if defined(__ppc__) || defined(__ppc64__)
#define ARCH_PPC
#elif defined(__i386__)
worksrcdir ${name}
And added:
dist_subdir ${name}/${version}
See attached.
The Portfile works great.
Thank again!
Rob
From: Ryan Schmidt
Sent: August 5, 2022 4:29 PM
To: Robert Kennedy
Cc: Joshua Root ; MacPorts Developers
Subject: Re
d in these circumstances considering that the garbled output
does not appear to affect building the final binary? Should I turn off
parallel builds in the Portfile?
Rob
From: Robert Kennedy
Sent: August 1, 2022 10:54 AM
To: Joshua Root
Cc: MacPorts Development
used in the code since as you
pointed out Intel Macs are little little-endian.
Rob
From: Ryan Schmidt
Sent: August 5, 2022 8:33 PM
To: Robert Kennedy
Cc: MacPorts Developers
Subject: Re: Issues with config.h
On Aug 5, 2022, at 16:43, Robert Kennedy wrote:
>
Ryan and Josh,
Thank you again for helping me with my new port M2VDownsizer.
FYI -- I have submitted a Pull Request and am happy to see that it builds fine
on MacOS 11 and MacOS 12.
See
https://github.com/macports/macports-ports/pull/15636
I still find it strange that the HAVE_STDINT_H macro g
Mark,
The Makefile template that you sent me looks like it was based on a Makefile
template for C programs, NOT C++ programs.
For C++, you need to set CXX to the compiler and use CXXFLAGS for the C++
compiler flags. Use +=. Do not use := since MacPorts will likely want to add
its own flags.
I have been experimenting with building my M2VDownsizer port on other Macs
running newer MacOS. M2VDownsizer uses a Makefile to build the binary from
source code written in C. (see PR
https://github.com/macports/macports-ports/pull/15636 )
I find that on newer Macs (e.g. 10.13), the followi
ally not a Macports issue but a macOS issue.
Rob
From: macports-dev on behalf of
Robert Kennedy
Sent: August 16, 2022 7:17 PM
To: macports-dev@lists.macports.org
Subject: ld: waning messages -- Frameworks out of sync.
I have been experimenting with building my M
Thanks Ken!
Letting me know that the "tapi" command is the key to the fix was a big help.
I did a quick google search for "tapi stubify" and found that someone has
already created a ruby script to fix the problem. But one needs to disable
System Integrity Protection (SIP) first before running
Over a week ago, I submitted an Pull Request to upgrade the totp-cli port to
version 1.2.5.
See https://github.com/macports/macports-ports/pull/17418
The upgraded port used to build just fine on Lion and Mtn Lion.
But after upgrading to Macprts 2.8.1 this morning, the port no longer builds on
L
roblem with building
the go-1.4 port.
Now if I can only get the totp-cli port to build using MacPorts v2.8.1.
Rob
From: macports-dev on behalf of
Robert Kennedy
Sent: January 31, 2023 12:49 PM
To: macports-dev@lists.macports.org
Subject: Problem Building Port
.
Rob
From: Joshua Root
Sent: January 31, 2023 3:43 PM
To: Robert Kennedy
Cc: MacPorts Development
Subject: Re: Problem Building Port After Upgrading Macports from 2.8.0 to 2.8.1
On 1/2/2023 04:49, Robert Kennedy wrote:
> Error: Failed to extract totp-
,
Rob
From: Joshua Root
Sent: January 31, 2023 4:27 PM
To: Robert Kennedy
Cc: MacPorts Development
Subject: Re: Problem Building Port After Upgrading Macports from 2.8.0 to 2.8.1
If you sync from git you will get the change immediately. For rsync it
can take up
Three weeks ago, I submitted a Pull Request for totp-cli. (see
https://github.com/macports/macports-ports/pull/17418).
But the PR has not been assigned to anyone for a review and merge. It is a
simple update to an existing port. It should be fairly straightforward.
When someone gets a chance,
Earlier today, I submitted a Pull Request to fix and update the star port to
version 1.6.
see https://github.com/macports/macports-ports/pull/18616
The updated star port works just fine on my Mac running High Sierra.
But it is failing on Big Sur and above according to the buildbot. But it is
I am unable to fetch a file in a git repo using MacPorts. I get an SSL expired
error.
fatal: unable to access 'https://codeberg.org/schilytools/schilytools.git/':
SSL certificate problem: certificate has expired
Command failed: /usr/bin/git clone --progress --depth=1
https://codeberg.org/schi
Thanks Joshua. That was exactly what was needed.
Perhaps a ticket should be created recommending that "git.cmd" be added to the
MacPorts Guide.
Rob
From: Joshua Root
Sent: May 17, 2023 4:47 AM
To: Robert Kennedy ; MacPorts Development
Subject: R
I am upgrading a port where only certain installed releases will prevent the
building of the upgraded port.
Is there a way to use conflicts_build from the conflicts_build PortGroup with
only certain installed releases? Maybe it could be done by using a pre-build
{} tcl block?
Is there a globa
From: macports-dev on behalf of
Robert Kennedy
Sent: May 20, 2023 9:47 AM
To: macports-dev@lists.macports.org
Subject: Need Help with the "conflicts_build" PortGroup
I am upgrading a port where only certain installed releases will prevent the
building of the upgraded port.
I have been working on a number of ports which depend on a recent version of
smake to build them. Unfortunately, the version of smake in the MacPorts repo
is just too old to build new software that use the Schily SING Makefile system.
I have submitted a Pull Request (PR) to update smake. Pleas
29 matches
Mail list logo
