#40513 closed defect (fixed)
codeblocks: universal variant fails
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | mojca (Mojca Miklavec) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia), cooljeanius (Eric Gallager) | |
| Port: | codeblocks |
Description
clang: error: cannot use 'precompiled-header' output with multiple -arch options
Change History (9)
comment:1 follow-up: 3 Changed 11 years ago by mojca (Mojca Miklavec)
comment:2 Changed 11 years ago by mojca (Mojca Miklavec)
| Cc: | jeremyhu@… added |
|---|---|
| Version: | 2.2.0 |
comment:3 Changed 11 years ago by cooljeanius (Eric Gallager)
Replying to mojca@…:
I would be grateful for hints about how to disable precompiled headers. Maybe this is something that could/should go to FAQ.
A tiny bit is written here: http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html
There should be a configure flag for it, if not, there should be some Autoconf macros to handle that, which could be used in a patch for the configure.ac file. I know that bakefile's bakefile.m4 macro file has stuff relating to precompiled headers in it, for example...
comment:6 follow-up: 7 Changed 11 years ago by mojca (Mojca Miklavec)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I have found
--enable-pch=no
and committed it in r111287.
This seems like a weird way, I would expect a flag --disable-pch, but well ...
comment:7 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to mojca@…:
I have found
--enable-pch=noand committed it in r111287.
This seems like a weird way, I would expect a flag
--disable-pch, but well ...
codeblocks uses an autotools-based configure script, therefore "--enable-foo=no" is the same as "--disable-foo", just as "--enable-foo=yes" is the same as "--enable-foo".
comment:8 follow-up: 9 Changed 11 years ago by mojca (Mojca Miklavec)
OK, I was expecting an explicit --disable-pch to appear somewhere in configure script, but I see now that there is an option wildcard at the beginning of the file. I knew that --disable-foo was supposed to be the same as --enable-foo=no, but I thought that implementation for this particular option was lacking something.
But I hope that universal build works for you now?
I would be grateful for hints about how to disable precompiled headers. Maybe this is something that could/should go to FAQ.
A tiny bit is written here: http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html