Opened 17 months ago
Last modified 2 days ago
#67509 assigned defect
Building lame on Tiger fails as the SDK name is incorrect — at Version 4
Reported by: | RealKGB (WhitetailAni) | Owned by: | barracuda156 |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | tiger | Cc: | |
Port: | lame |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I am attempting to install ffmpeg on my iMac G5 running OS X 10.4.11. One of the required dependencies is lame, but when trying to build, it produces the log attached below.
When looking in the log and looking up the errors, the reoccurring one is expected '=', ',', ';', 'asm' or '__attribute__' before 'size_t'
- which means this is C++ code, that a C compiler is trying to compile. I've attached the log if that helps at all.
Change History (5)
Changed 17 months ago by RealKGB (WhitetailAni)
comment:1 Changed 17 months ago by kencu (Ken)
the problem is this recent commit is wrong for Tiger:
[ad0b70302b368b8da1342fd586db04ffce1f6fe5/macports-ports]
In Tiger, the SDK name is different than all other systems…. there is a “u” in it.
The commit needs to be rejigged to account for this.
comment:2 Changed 17 months ago by kencu (Ken)
Keywords: | Tiger added |
---|---|
Owner: | set to barracuda156 |
Status: | new → assigned |
Summary: | Building lame on OS X 10.4.11 on an iMac G5 fails; it seems to be attempting to build C++ code with a C compiler → Building lame on Tiger fails as the SDK name is incorrect |
comment:3 Changed 17 months ago by kencu (Ken)
also not all ppc systems support altivec, so that should be fixed too
comment:4 Changed 17 months ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Keywords: | tiger added; Tiger removed |
I wonder why that commit is setting the SDK path manually. Doesn't MacPorts already set it?
Log that occurs when building lame