| Summary: | app-editors/vim-7.2.303 with et_EE locale - In file included from vim.h:282, from buffer.c:28: auto/osdef.h:18: error: conflicting types for 'printf' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Rainer <vabamae> |
| Component: | Current packages | Assignee: | Vim Maintainers <vim> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | leho |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
environment log output of ./configure The correct config.log auto/osdef |
||
|
Description
Rainer
2010-06-22 19:34:29 UTC
Full build log and config.log would be useful here. Created attachment 237171 [details]
build.log
Created attachment 237173 [details]
environment log
Lets try with config.log again. Probably that generated auto/osdef.h could be helpful too. Created attachment 237477 [details]
output of ./configure
Comment on attachment 237477 [details]
output of ./configure
I am not sure how to get this osdef file
Well, third time's the charm - attach 'config.log' - that one of the files, configure script produces, where the correctly written checks tend to leave more info than the console output of configure. The other file is obviously in the source tree after it gets generated during CC="i686-pc-linux-gnu-gcc -Iproto -DHAVE_CONFIG_H -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -I/usr/lib/perl5/5.8.8/i686-linux/CORE -I/usr/include/python2.6 -pthread " srcdir=. sh ./osdef.sh Created attachment 237591 [details]
The correct config.log
Created attachment 237593 [details]
auto/osdef
OK, one more thing: see if you can emerge it while LC_ALL is set to i.e 'C' or 'en_US.UTF-8'. On that note (regarding your environment): it should be enough to set LANG, LC_ALL is mainly for overrides. Same thing with en_US.UTF-8 and same with C. (In reply to comment #10) > OK, one more thing: see if you can emerge it while > LC_ALL is set to i.e 'C' or 'en_US.UTF-8'. > > On that note (regarding your environment): it should be enough to set LANG, > LC_ALL is mainly for overrides. > My bad, forgot to update environment. With en_US-UTF-8 compiles well. How can I compile with my proper localization? (In reply to comment #11) > Same thing with en_US.UTF-8 and same with C. > > > (In reply to comment #10) > > OK, one more thing: see if you can emerge it while > > LC_ALL is set to i.e 'C' or 'en_US.UTF-8'. > > > > On that note (regarding your environment): it should be enough to set LANG, > > LC_ALL is mainly for overrides. > > > OK, time to assign. et_EE is often a problem, due to a-z not covering the whole ASCII alphabet. It's a valid bug though. However, it's strange it wasn't reported earlier, so probably either the problem will be on your side or recently a not quite thought out change was introduced somewhere in the build system. ok, running into the same problem here, also on et_EE. strange thing is 303 compiles, but everything from 442 on fails. sudo ACCEPT_KEYWORDS=~x86 LC_ALL=en_US-UTF-8 emerge -va vim succeeds for me (currently ~7.3) I don't think I've seen this in the 7.4 branch at all. Recommend closing this bug. (In reply to Leho Kraav (:macmaN @lkraav) from comment #15) |
