Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

_XOPEN_SOURCE and _POSIX_C_SOURCE warnings when building on Linux #1

Closed
sunyab opened this issue Jul 26, 2016 · 4 comments
Closed

_XOPEN_SOURCE and _POSIX_C_SOURCE warnings when building on Linux #1

sunyab opened this issue Jul 26, 2016 · 4 comments
Assignees
@pixar-oss

Comments

@sunyab
Copy link
Contributor

sunyab commented Jul 26, 2016

Platform: RHEL7
Compiler Version: gcc 4.8.5

When building USD on Linux, we get many warnings due to redefinitions of the _XOPEN_SOURCE and _POSIX_C_SOURCE macros. This is likely due to Python headers not being included at the top of files as required (see https://docs.python.org/2/c-api/intro.html#include-files). We should be able to fix this by moving these headers up in the include order.
@mistafunk
Copy link

unsurprisingly, i'm seeing the same on gentoo linux

@amooty
Copy link

amooty commented Aug 2, 2016

Filed as internal issue #135152.

@aloysbaillet aloysbaillet mentioned this issue Oct 18, 2016
Open
@spiffmon spiffmon mentioned this issue Jan 6, 2017
Closed
@sunyab sunyab assigned sunyab and pixar-oss and unassigned sunyab Mar 10, 2017
@sunyab
Copy link
Contributor Author

sunyab commented Mar 10, 2017

Commit 27fcbaf adds a workaround for this issue. In my local builds, I no longer receive these warning messages. The bigger issue of reordering Python includes to accommodate their requirements still exists, but we hope to address that when we take a closer look at how we structure our Python-related code.

Thanks to @sirpalee for suggesting the workaround on the usd-interest forum!

@spiffmon spiffmon mentioned this issue Mar 24, 2017
Closed
@sunyab
Copy link
Contributor Author

sunyab commented May 2, 2017

This is fixed in 27fcbaf in release 0.7.5. Closing.

@sunyab sunyab closed this as completed May 2, 2017
@alexwheezy alexwheezy mentioned this issue Jun 19, 2017
Closed
pixar-oss pushed a commit that referenced this issue Feb 15, 2018
@rajabala @pixar-oss
[Hd] Edge selection #1 (Selection API update and buffer encoding upda…
7b11dd7 
…te for edges)

Extended the HdxSelection API for edges.
Reworked the selection buffer encoding to be more extensible for subprimitives (elements, edges and points). This includes encoding (CPU) and decoding (GPU).
Added placeholders for Is{Edge,Point}Selected in the shader code.
Previously, the non-{0,1} offsets in the selection buffer were relative to the selection mode, which made the decoding trickier. Now, they're absolute indices in the buffer.

(Internal change: 1827347)
@asluk asluk mentioned this issue May 8, 2019
Closed
@thang12l thang12l mentioned this issue Dec 28, 2019
Closed
@spitzak spitzak mentioned this issue Jul 26, 2021
Closed
@spiffmon spiffmon mentioned this issue Feb 5, 2022
Open
This was referenced Feb 9, 2022
Open
Closed
Closed
Open
Open
@tcauchois tcauchois mentioned this issue May 12, 2022
Open
@dtoshevcg dtoshevcg mentioned this issue May 16, 2024
Open
@spiffmon spiffmon mentioned this issue Jul 23, 2024
Open
@tcauchois tcauchois mentioned this issue Sep 12, 2024
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pixar-oss pixar-oss

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mistafunk @sunyab @amooty @pixar-oss