Bug 243218 - graphics/openshadinglanguage: Fails to build on 13.0-CURRENT: llvm_ops.s:124:44: error: expected ')' at end of argument list
Summary: graphics/openshadinglanguage: Fails to build on 13.0-CURRENT: llvm_ops.s:124:...
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2020-01-09 12:56 UTC by Lorenzo Salvadore
Modified: 2020-01-12 09:30 UTC (History)
1 user (show)

See Also:
koobs: merge-quarterly?

Attachments
openshadinglanguage build error (3.28 KB, text/plain)
2020-01-09 12:56 UTC, Lorenzo Salvadore 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lorenzo Salvadore freebsd_committer 2020-01-09 12:56:58 UTC 
Created attachment 210566 [details]
openshadinglanguage build error

I attach the log of the failure.
Comment 1 Shane 2020-01-11 07:05:25 UTC 
From the build log I see you are building within /usr/obj/usr/ports. I expect you are seeing a conflict between base and newly built system binaries. 

Is this x86? cross compiling?
New system svn revision? Base sys rev?

Do you normally test build ports this way?
Does it work if you build in the base system /usr/ports?
Comment 2 Lorenzo Salvadore freebsd_committer 2020-01-12 09:30:38 UTC 
> Is this x86? cross compiling?
It is amd64, not cross compiling.

> New system svn revision? Base sys rev?
Ports tree revision is 522170 (head).
Src revision is 356358.

> Do you normally test build ports this way?
Yes, I normally build ports this way: I have 430 ports installed that way on my system right now.

> Does it work if you build in the base system /usr/ports?
The build fails if I build in the base system /usr/ports, i.e. if I set WRKDIRPREFIX=
I also tried to build with __MAKE_CONF=/dev/null and the build still fails with the same error.

Thanks for working on it.