This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Problems to build OpenSwan (IPSec-Tools patching)

Hi,

i followed the instructions "http://processors.wiki.ti.com/index.php/Build_OpenSwan_for_Sitara".

I've a problem to patch the IPSec-Tools. The patch 0001-Fix-Patch.patch was copied to /home/osboxes/image/ipsec-tools-0.8.2/src.

The execution of the patch starts as follow:

[linux-devkit]:/home/osboxes/Image> patch -p1 < 0001-Fix-Patch.patch<code>
bash: syntax error near unexpected token `newline'

If the patch is execute in the way i understand the description (replace <code> with ./configure $CONFIGURE_FLAGS...) , a error occured:

[linux-devkit]:/home/osboxes/Image> patch -p1 < 0001-Fix-Patch.patch ./configure $CONFIGURE_FLAGS --with-kernel-headers=/opt/ti-sdk-am335x-evm-07.00.00.00/board-support/kernel-headers/include --enable-security-context=no --prefix=/usr/
bash: 0001-Fix-Patch.patch: No such file or directory

==> The directory /opt/ti-sdk-am335x-evm-07.00.00.00/board-support/kernel-headers/include exists.

 

What's the meaninig of this instruction, what ist exactly executed:

patch -p1 < 0001-Fix-Patch.patch<code> 
<code>./configure $CONFIGURE_FLAGS --with-kernel-headers=<sdk-path>/board-support/kernel-headers/include --enable-security-context=no --prefix=/usr/

 

Yours Stefan

  • Hi Stefan,

    I will forward this to the SW team, but response will probably be delayed until the holidays are over.

  • Hi,

    the problem is solved. The description isn't so clear for the location of the patch file. The description means, that the patch file located in the source directory (ipsec-tools-x.x.x/src) but the patching fails. The correct location for the patch file is into the ipsec-tools-x.x.x directory.
    After patching the execution of the configuration follows:./configure $CONFIGURE_FLAGS --with-kernel-headers=<sdk-path>/board-support/kernel-headers/include --enable-security-context=no --prefix=/usr/


    The meaning of <source> is not clear, because yet not a problem.

    Yours,

    Stefan