On Thu, Jan 17, 2013 at 5:51 AM, Jon Schipp <[email protected]> wrote:
> I did a 'make clean' earlier and rebuilt it again on Fedora and it worked.
>
> Back on Ubuntu 12.04-amd64. Yes, the rest of the tools compile fine.
>
> $ make --version
> GNU Make 3.81
>
> $ bash --version
> GNU bash, version 4.2.24(1)-release (x86_64-pc-linux-gnu)
>
> $ make Q= curvetun
> NACL_LIB_DIR/NACL_INC_DIR is undefined, building libnacl with curvetun!
> echo "Building nacl:"
> Building nacl:
> cd curvetun/ && ./build_nacl.sh ~/nacl
> Building NaCl for arch amd64 on host ubuntu (grab a coffee, this takes
> a while) ...
> NaCl lib path /root/nacl/nacl-20110221/build/ubuntu/lib/amd64
> NaCl include path /root/nacl/nacl-20110221/build/ubuntu/include/amd64
> ./nacl_path.sh: 20: ./nacl_path.sh: source: not found
> Done!
> source ~/.bashrc
> /bin/sh: 1: source: not found
> make: *** [nacl] Error 127
>
> I did a manual source and it worked after:
> $ source ~/.bashrc

This was very helpful! Thanks!

I just did a commit, could you give it a new try in case you have some time?

> On Tue, Jan 15, 2013 at 5:50 PM, Daniel Borkmann <[email protected]> 
> wrote:
>> On Tue, Jan 15, 2013 at 3:08 AM, Jon Schipp <[email protected]> wrote:
>>> FYI: I get this on Fedora 17 x86_64
>>>
>>> Building NaCl for arch amd64 on host fedora17 (grab a coffee, this
>>> takes a while) ...
>>> NaCl lib path /root/nacl/nacl-20110221/build/fedora17/lib/amd64
>>> NaCl include path /root/nacl/nacl-20110221/build/fedora17/include/amd64
>>> Done!
>>> Building curvetun:
>>
>> Can you please post me what can be seen via "make Q= curvetun" ... the
>> rest of the tools, I assume compile fine on your side?
>>
>>> Makefile:227: warning: undefined variable `NACL_INC_DIR'
>>>   CC    xmalloc.c
>>> gcc: error: curvetun/xmalloc.o: No such file or directory
>>> make: *** [curvetun/xmalloc.o] Error 1
>>
>> Fedora 17, x86_64, on my laptop:
>>
>> # make --version
>> GNU Make 3.82
>> Built for x86_64-redhat-linux-gnu
>>
>> # bash --version
>> GNU bash, version 4.2.39(1)-release (x86_64-redhat-linux-gnu)
>>
>> # make
>> Building netsniff-ng toolkit (0.5.8-rc0) for x86_64-redhat-linux:
>> Building netsniff-ng:
>>   CC    hash.c
>>   CC    dissector.c
>>   CC    dissector_eth.c
>>   CC    dissector_80211.c
>>   CC    proto_arp.c
>>   CC    proto_ethernet.c
>>   CC    proto_icmpv4.c
>>   CC    proto_icmpv6.c
>>   CC    proto_igmp.c
>>   CC    proto_ip_authentication_hdr.c
>>   CC    proto_ip_esp.c
>>   CC    proto_ipv4.c
>>   CC    proto_ipv6.c
>>   CC    proto_ipv6_dest_opts.c
>>   CC    proto_ipv6_fragm.c
>>   CC    proto_ipv6_hop_by_hop.c
>>   CC    proto_ipv6_in_ipv4.c
>>   CC    proto_ipv6_mobility_hdr.c
>>   CC    proto_ipv6_no_nxt_hdr.c
>>   CC    proto_ipv6_routing.c
>>   CC    proto_none.c
>>   CC    proto_tcp.c
>>   CC    proto_udp.c
>>   CC    proto_vlan.c
>>   CC    proto_vlan_q_in_q.c
>>   CC    proto_mpls_unicast.c
>>   CC    proto_80211_mac_hdr.c
>>   CC    xio.c
>>   CC    xutils.c
>>   CC    xmalloc.c
>>   CC    bpf.c
>>   CC    oui.c
>>   CC    pcap.c
>>   CC    pcap_rw.c
>>   CC    pcap_sg.c
>>   CC    pcap_mmap.c
>>   CC    mac80211.c
>>   CC    ring_rx.c
>>   CC    ring_tx.c
>>   CC    tprintf.c
>>   CC    netsniff-ng.c
>>   LD    netsniff-ng
>>   STRIP netsniff-ng
>> Building trafgen:
>>   LEX   trafgen_lexer.l
>>   YAAC  trafgen_parser.y
>>   CC    xmalloc.c
>>   CC    xio.c
>>   CC    xutils.c
>>   CC    mac80211.c
>>   CC    ring_tx.c
>>   CC    trafgen/trafgen_lexer.yy.c
>>   CC    trafgen/trafgen_parser.tab.c
>>   CC    trafgen.c
>>   LD    trafgen
>>   STRIP trafgen
>> Building astraceroute:
>>   CC    xmalloc.c
>>   CC    xio.c
>>   CC    xutils.c
>>   CC    proto_none.c
>>   CC    tprintf.c
>>   CC    aslookup.c
>>   CC    bpf.c
>>   CC    mtrand.c
>>   CC    ring_rx.c
>>   CC    astraceroute.c
>>   LD    astraceroute
>>   STRIP astraceroute
>> Building flowtop:
>>   CC    xmalloc.c
>>   CC    xio.c
>>   CC    xutils.c
>>   CC    oui.c
>>   CC    hash.c
>>   CC    dissector_eth.c
>>   CC    dissector_80211.c
>>   CC    dissector.c
>>   CC    proto_none.c
>>   CC    tprintf.c
>>   CC    flowtop.c
>>   LD    flowtop
>>   STRIP flowtop
>> Building ifpps:
>>   CC    xmalloc.c
>>   CC    xio.c
>>   CC    xutils.c
>>   CC    ifpps.c
>>   LD    ifpps
>>   STRIP ifpps
>> Building bpfc:
>>   LEX   bpf_lexer.l
>>   LEX   bpf_hla_lexer.l
>>   YAAC  bpf_parser.y
>>   YAAC  bpf_hla_parser.y
>>   CC    xmalloc.c
>>   CC    xutils.c
>>   CC    bpf.c
>>   CC    bpf_symtab.c
>>   CC    bpfc/bpf_lexer.yy.c
>>   CC    bpfc/bpf_parser.tab.c
>>   CC    bpfc/bpf_hla_lexer.yy.c
>>   CC    bpfc/bpf_hla_parser.tab.c
>>   CC    bpfc.c
>>   LD    bpfc
>>   STRIP bpfc
>> Building curvetun:
>>   CC    xmalloc.c
>>   CC    xio.c
>>   CC    xutils.c
>>   CC    stun.c
>>   CC    mtrand.c
>>   CC    patricia.c
>>   CC    trie.c
>>   CC    hash.c
>>   CC    curve.c
>>   CC    ct_cpusched.c
>>   CC    ct_usermgmt.c
>>   CC    ct_servmgmt.c
>>   CC    ct_server.c
>>   CC    ct_client.c
>>   CC    curvetun.c
>>   LD    curvetun
>>   STRIP curvetun
>>
>>
>>> On Thu, Jan 10, 2013 at 2:59 AM, Daniel Borkmann <[email protected]> 
>>> wrote:
>>>> This doesn't make any sense to me.
>>>>
>>>> You still get the same error (like ``source'' not found)?
>>>>
>>>> As you know, it's there to re-read the .bashrc file.
>>>>
>>>> Could you provide me some more debugging information?
>>>>
>>>> Like running strace on the nacl_path script and do the curvetun build
>>>> with Q=  "make Q= curvetun".
>>>>
>>>> Then, I could see what's going on here.
>>>>
>>>> Markus, is your curvetun build working on Ubuntu/Debian?
>>>>
>>>> On Thu, Jan 10, 2013 at 12:39 AM, Jon Schipp <[email protected]> wrote:
>>>>> My default shell is bash and I've only used the root account.
>>>>> .bashrc does have the lines:
>>>>> export NACL_INC_DIR=/root/nacl/nacl-20110221/build/ubuntu/include/amd64
>>>>> export NACL_LIB_DIR=/root/nacl/nacl-20110221/build/ubuntu/lib/amd64
>>>>>
>>>>> On Mon, Dec 10, 2012 at 5:30 AM, Daniel Borkmann <[email protected]>
>>>>> wrote:
>>>>>>
>>>>>> hat you built the first time NaCl under root and then
>>>>>> compiled the toolkit as a user?
>>>>>
>>>>>
>>
>> --
>>
>>
>
> --
>
>

-- 


Reply via email to