kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

Bob, it's actually funny.  I don't upgrade my build machines without
updating my test machine first.

Over the weekend, I decided to upgrade my test machine, to prep for
updating the build machine.  Before doing the update, I made a build on my
test machine, to prove it works before making the changes.  This is the
outcome of that build :)

Adam Wolf

On Mon, Apr 27, 2015 at 11:33 AM, Bob Gustafson <bobgus@xxxxxxx> wrote:

>  Hi Adam
>
> Perhaps it was an upgrade of your build machine from 10.10.2 to 10.10.3 ?
>
> Bob g
>
>
> On 04/27/2015 10:56 AM, Garth Corral wrote:
>
> Hi, Adam.  Sorry I hadn’t looked at this previously, I’ve not seen this
> issue.
>
>  I likely won’t have a chance to look at this until late today at the
> earliest, but just a quick glance makes me suspect a deployment target
> issue.  I don’t have a system on which to verify at the moment, but I don’t
> think fchmodat was supported prior to 10.10.
>
>
>  Garth
>
>
>  On Apr 27, 2015, at 7:56 AM, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
> wrote:
>
>  Hmm.  This is starting to concern me.
>
>  When I checked out KiCad from source, and ran an appropriate cmake/make
> against it, this happened again.
>
>  When I reran cmake/make in my existing source/build directory pair, this
> did not happen.  I checked bzr status to see if I had any modifications,
> and I did not.
>
>  I then copied my existing source/build directory pair, and deleted
> everything that is listed in .bzrignore.  This happened again.
>
>  I have a line in my build scripts that I thought deleted/reverted
> anything not from bzr in the bzr directories, but I guess it ignores what
> is in bzrignore!
>
>  Anyway, long story short, I don't know if I can make any new builds
> right now.  The nightlies will still come out, due to caching in something
> in bzrignore, (boost perhaps?).
>
>  Anyway, I'll continue debugging this but if anyone has any insight,
> please let me know.
>
>  Adam Wolf
> Cofounder and Engineer
> W&L
>
> On Sat, Apr 25, 2015 at 9:27 PM, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>
> wrote:
>
>> Hi folks,
>>
>>  Anyone ever see this before?
>>
>>  clang: warning: argument unused during compilation: '-XLinker,-cref'
>> clang: warning: argument unused during compilation:
>> '-XLinker,-Map=_pcbnew.kiface.map'
>> Undefined symbols for architecture x86_64:
>>   "_fchmodat", referenced from:
>>       boost::filesystem::detail::permissions(boost::filesystem::path
>> const&, boost::filesystem::perms, boost::system::error_code*) in
>> libboost_filesystem.a(operations.o)
>> ld: symbol(s) not found for architecture x86_64
>> clang: error: linker command failed with exit code 1 (use -v to see
>> invocation)
>> make[2]: *** [kicad/kicad.app/Contents/PlugIns/_pcbnew.kiface] Error 1
>> make[1]: *** [pcbnew/CMakeFiles/pcbnew_kiface.dir/all] Error 2
>>
>>  Stack Overflow says that I should be linking against
>> libboost_filesystem.dylib. I'll take a look, but wondering if anyone has
>> seen this before.
>>
>>  Adam Wolf
>> Cofounder and Engineer
>> W&L
>>
>
>  _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>